Details
-
Bug
-
Status: Resolved
-
P3
-
Resolution: Fixed
-
None
Description
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.
Attachments
Issue Links
- relates to
-
BEAM-9082 "Socket closed" Spurious GRPC errors in Flink/Spark runner log output
- Open
- links to