Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.11.2
    • Fix Version/s: 1.12.0, 1.11.3
    • Component/s: Runtime / Coordination
    • Labels:
      None

      Description

      The OperatorCoordinator.resetToCheckpoint() currently lacks the information which checkpoint it recovers to.

      That forces implementers to assume strict ordering of method calls between restore and failure. While that is currently guaranteed in this case, it is not guaranteed in other places (see parent issue).

      Because of that, we want implementations to not assume method order at all, but rely on explicit information passed to the methods (checkpoint IDs). Otherwise we end up with mixed implementations that partially infer context from the order of method calls, and partially use explicit information that was passed.

        Attachments

          Activity

            People

            • Assignee:
              sewen Stephan Ewen
              Reporter:
              sewen Stephan Ewen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: