Uploaded image for project: 'Apache Apex Core'
  1. Apache Apex Core
  2. APEXCORE-619

recovery window id in future for terminating state less operators during relaunch.

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              tushargosavi Tushar Gosavi
              Reporter:
              tushargosavi Tushar Gosavi
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: