1

Resolved

Server fails to identify idle batches

description

The server mistakes inactive batches as active batches. Then when an idle node requests the next batch, the server responds that none exists when in fact there are multiple batches ready.
 
This is a blocking issue that must be resolved.

comments

joes wrote May 13, 2008 at 4:49 PM

I added code to check if the node is doing something different than what the server thinks to reset the state locally. This should resolve the issue we had with nodes getting started spuriously.

wrote May 13, 2008 at 4:49 PM

wrote Feb 1, 2013 at 4:35 AM

wrote May 14, 2013 at 6:44 AM

wrote May 14, 2013 at 6:44 AM

wrote Jun 4, 2013 at 1:55 AM