search

dmwm / PHEDEX

CMS data-placement suite
8 stars 18 forks source link

API to expose t_dps_block_dest? #951

Open TonyWildish opened 10 years ago

TonyWildish commented 10 years ago

while investigating a problem with Vlad I found a subscription was not moving because: 1) a prior subscription had filled the queue to the destination 2) the only source of the data for that subscription was on a host that had DNS problems, so it came and went from the agent-status page 3) a later subscription, from a different source to the same destination, was not queued for transfer.

The reason is that the first subscription blocked the queue, but never moved. You could see this in the t_dps_block_dest table where the status was -1 ("Assigned but not yet active (router could not activate into t_xfer_request because the priority queue is full)")

This did not show up as a backlog in the 'Volume Requested' plot. AFAICT, the only way to extract this information is to examine the table with sqlplus!

We need a better way to expose this information.

nikmagini commented 9 years ago

Hi,

this information is available through the t_dps_block_arrive table exposed through the corresponding blockarrive datasvc API. We just need a website page for more convenient viewing.

N.