Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-3976

SdkHarnessClient is thread-safe

Details

    • Bug
    • Status: Resolved
    • P2
    • Resolution: Not A Problem
    • None
    • Not applicable
    • runner-core
    • 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

          Activity

            People

              axelmagn Axel Magnuson
              bsidhom Ben Sidhom
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: