You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2017/10/13 16:44:00 UTC

[jira] [Reopened] (BEAM-3016) BeamFnLoggingClient shutdown stability

     [ https://issues.apache.org/jira/browse/BEAM-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luke Cwik reopened BEAM-3016:
-----------------------------

Turns out this still flaked occasionally since the close() arriveAndDeregister and onReadyHandler() arrive calls may occur before the phaser advances putting the phaser into an illegal state.

> BeamFnLoggingClient shutdown stability
> --------------------------------------
>
>                 Key: BEAM-3016
>                 URL: https://issues.apache.org/jira/browse/BEAM-3016
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-harness
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>            Priority: Minor
>              Labels: portability
>
> The BeamFnLoggingClient has a race condition where it may not shutdown appropriately if the channel has an error.
> This occurs because the stream observer created by the StreamObserverFactory may block indefinitely if the DirectStreamObserver is used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)