Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-2305

Stream processor should ensure previous container is stopped during a rebalance

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      In standalone, when we have a rebalance before the container has started successfully with the previous job model, OnJobModelExpired does a no-op. It happens since the stream processor doesn’t transition to RUNNING until the container callback gets invoked. OnJobModelExpired, assumes the processor is still in the REBALANCE phase and does a no-op.

       

      Often times, containers take longer time to start. Especially stateful containers that have large state to restore. In those scenarios, if a rebalance happens before the container has started successfully, processors in the quorum will run with inconsistent job model.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bharathkk Bharath Kumarasubramanian
                Reporter:
                bharathkk Bharath Kumarasubramanian
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 5h 40m
                  5h 40m