[
https://issues.apache.org/jira/browse/BEAM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Cwik updated BEAM-3811:
----------------------------
Fix Version/s: 2.35.0
Resolution: Fixed
Status: Resolved (was: Open)
> 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: 4.5h
> 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)
