Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-12475

When bundle processors are re-used, do not respond to splits for previous bundles.

Details

    • Bug
    • Status: Resolved
    • P1
    • Resolution: Fixed
    • 2.30.0
    • 2.31.0
    • java-fn-execution
    • None

    Description

      The error manifests in the following way:

      (thread1) Start processing bundle A
      (thread2) Receive request to split for bundle A
      (thread1) Finish bundle A
      (thread1) Reset bundle processor
      (thread1) Start processing bundle B
      (thread2) Process split for bundle A on bundle B

      Runners, such as Dataflow, that ensure the self-reported number of elements processed by the SDK is equal to the number they expected to be processed (taking into account the runner's understanding of all splits) can detect this and reject A and B as invalid, but we should fix this race condition.

      Attachments

        Activity

          People

            robertwb Robert Bradshaw
            robertwb Robert Bradshaw
            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 - 7h 40m
                7h 40m