[
https://issues.apache.org/jira/browse/BEAM-10959?focusedWorklogId=491237&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-491237
]
ASF GitHub Bot logged work on BEAM-10959:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Sep/20 14:05
Start Date: 25/Sep/20 14:05
Worklog Time Spent: 10m
Work Description: lukecwik edited a comment on pull request #12934:
URL: https://github.com/apache/beam/pull/12934#issuecomment-698948854
> @lukecwik is there documentation for the control stream mentioned in the
bug?
@udim What detail are you looking for?
* how the control stream is used to process a bundle:
https://s.apache.org/beam-fn-api-processing-a-bundle
* how the control stream is used to report progress:
https://s.apache.org/beam-fn-api-progress-reporting
* gRPC streams are ordered: https://grpc.io/docs/what-is-grpc/core-concepts/
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 491237)
Time Spent: 3h 50m (was: 3h 40m)
> Fix race where split/progress calls return "Unknown process bundle
> instruction"
> -------------------------------------------------------------------------------
>
> Key: BEAM-10959
> URL: https://issues.apache.org/jira/browse/BEAM-10959
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Reporter: Luke Cwik
> Assignee: Luke Cwik
> Priority: P2
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Currently there is a race where a BundleProcessor doesn't exist until another
> thread picks up the task and inserts into the active set. This allows for
> split/progress calls to happen and error out with "Unknown process bundle
> instruction X".
> Since the control stream is ordered, we can guarantee that an uninitialized
> BundleProcessor exists that can respond to this really early split/progress
> calls.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
