Open Stack

Hi,

We suffered a hung object replicator recently. In the process of sorting 
that out some question came to mind:

1/ Reliably determining if a replicator has hung (or just has nothing to do)

2/ Determining how behind replication is


Now the output of swift-recon combined with the dispersion report 
certainly *suggest* that (say in case 1) there is work to do but nothing 
is happening. However is there a known way to determine that 'ok chaps 
the replicator has hung...'?


Along the same lines the next question I'm being asked is about 2/ 'How 
behind/how much work is left for the replicator'? From previous reading 
of the code it looks like the replicator creates jobs (each of which is 
a partition + a set of suffixes) - so is there a way to poke the daemon 
and ask something like 'how many jobs do you have to go this run'?


regards


Mark