Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Not A Problem
-
None
-
None
Description
In general, we want to share access to a given SDK harness among multiple runner workers as a way to amortize container startup and resource costs. Because control messages are multiplexed over the same shared control connection, this sharing currently requires external locking on the same shared lock object. This is error-prone and difficult to verify. The SdkHarnesClient should use internal mechanisms to provide thread-safety.
Attachments
Issue Links
- is depended upon by
-
BEAM-2889 Flink runs portable pipelines
- Resolved