[
https://issues.apache.org/jira/browse/BEAM-3811?focusedWorklogId=677823&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-677823
]
ASF GitHub Bot logged work on BEAM-3811:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Nov/21 20:41
Start Date: 05/Nov/21 20:41
Worklog Time Spent: 10m
Work Description: lukecwik merged pull request #15849:
URL: https://github.com/apache/beam/pull/15849
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 677823)
Time Spent: 5h 10m (was: 5h)
> Add a CancellableQueue to make close methods safer
> --------------------------------------------------
>
> Key: BEAM-3811
> URL: https://issues.apache.org/jira/browse/BEAM-3811
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Thomas Groh
> Assignee: Luke Cwik
> Priority: P3
> Labels: portability
> Fix For: 2.35.0
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> There are multiple locations in which, on a call to {{close}} within some
> portability service, we wish to close all of our outstanding clients.
> However, the call to {{close}} can be interleaved with calls to the method
> which creates a new client. Without having an explicit thread-safe signal
> from the collection of pending clients, there's no way to ensure that all of
> the clients for a service are closed when that service is closed.
>
> As a result, some clients are only terminated by the forceful termination of
> the server, killing the connection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
