You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2019/10/16 09:36:00 UTC
[jira] [Resolved] (BEAM-8403) Race condition in request id
generation of GrpcStateRequestHandler
[ https://issues.apache.org/jira/browse/BEAM-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels resolved BEAM-8403.
--------------------------------------
Resolution: Fixed
> Race condition in request id generation of GrpcStateRequestHandler
> ------------------------------------------------------------------
>
> Key: BEAM-8403
> URL: https://issues.apache.org/jira/browse/BEAM-8403
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.17.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> There is a race condition in {{GrpcStateRequestHandler}} which surfaced after the recent changes to process append/clear state request asynchronously. The race condition can occur if multiple Runner workers process a transform with state requests with the same SDK Harness. For example, this setup occurs with Flink when a TaskManager has multiple task slots and two or more of those slots process the same stateful stage against an SDK Harness.
> CC [~robertwb]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)