Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-13750

Separate HA services between client-/ and server-side

    XMLWordPrintableJSON

    Details

    • Release Note:
      Hide
      The `HighAvailabilityServices` have been split up into client side `ClientHighAvailabilityServices` and cluster side `HighAvailabilityServices`. When implementing your own high availability services, you should follow this separation by overriding the factory method `HighAvailabilityServicesFactory.createClientHAServices`. Moreover, `HighAvailabilityServices#getWebMonitorLeaderRetriever` should no longer be implemented since it has been deprecated.
      Show
      The `HighAvailabilityServices` have been split up into client side `ClientHighAvailabilityServices` and cluster side `HighAvailabilityServices`. When implementing your own high availability services, you should follow this separation by overriding the factory method `HighAvailabilityServicesFactory.createClientHAServices`. Moreover, `HighAvailabilityServices#getWebMonitorLeaderRetriever` should no longer be implemented since it has been deprecated.

      Description

      Currently, we use the same HighAvailabilityServices on the client and server. However, the client does not need several of the features that the services currently provide (access to the blobstore or checkpoint metadata).

      Additionally, due to how these services are setup they also require the client to have access to the blob storage, despite it never actually being used, which can cause issues, like FLINK-13500.

      Zili Chen Would be be interested in this issue?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tison Zili Chen
                Reporter:
                chesnay Chesnay Schepler
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m