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/15 10:00:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16951788#comment-16951788 ] 

Maximilian Michels commented on BEAM-8403:
------------------------------------------

Should add that the SdkHarness itself has to be configured with a worker count >1 for this to be visible. The default is 12.

> 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
>
>
> 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)