[APEXCORE-619] recovery window id in future for terminating state less operators during relaunch.

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Assignee: Tushar Gosavi
• Reporter: Tushar Gosavi
• Created: 23/Jan/17 10:28
• Updated: 01/Oct/17 14:34

Description

With following DAG

A -> B -> C

C is a stateless operator. If this application is killed and restarted after long time between kill and restart, then recovery window id of C is too high compare to A and B. This is because recovery windowid is computed from current timestamp for stateless operators in updateRecoveryCheckpoints.

The problem this causes

• Operator C does not process any data till windowId of B reached to recovery window id of C.
• If other operators are not able to keep up then C gets killed because it is detected as blocked operator.

Issue Links

• links to: GitHub Pull Request #490
• links to: GitHub Pull Request #490