View Revisions: Issue #1528

Summary 0001528: Routing can get stuck if there are lots of gaps that range across a large amount of data that has already been routed
Revision 2014-01-14 02:02 by chenson
Description Routing can get stuck if there are lots of gaps that range across a large amount of data that has already been routed.

The take() of data that needs to be routed, times out after a default of 330 seconds. If the reader takes longer than this to get past data that has already been routed, then the router job times out and starts over.

There is a flag that can be checked to see if a timed out job can start reading again.
Revision 2014-01-14 01:56 by chenson
Description Routing can get stuck if there are lots of gaps that range across a large amount of data that has already been routed.

The take() of data that needs to route times out after a default of 330 seconds. If the reader takes longer than this to get past data that has already been routed, then the router job times out and starts over.

There is a flag that can be checked to see if a timed out job can start reading again.