[ https://issues.apache.org/jira/browse/FLINK-13750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911247#comment-16911247 ]
Till Rohrmann commented on FLINK-13750: --------------------------------------- This sounds good to me. Maybe another thought. We could split {{HighAvailabilityServices}} up into {{ClientHighAvailabilityServices}} and {{ClusterHighAvailabilityServices}} and let {{HighAvailabilityServices}} extend both interfaces. That way we would decompose the original interface into smaller ones which could be passed into the respective using components {{ClientHighAvailabilityServices}} go into the {{ClusterClient}}, whereas {{ClusterHighAvailabilityServices}} go into the cluster components. This would, however, break binary backwards compatibility and people would need to recompile their custom implementations against the updated interface, I guess. > Separate HA services between client-/ and server-side > ----------------------------------------------------- > > Key: FLINK-13750 > URL: https://issues.apache.org/jira/browse/FLINK-13750 > Project: Flink > Issue Type: Improvement > Components: Command Line Client, Runtime / Coordination > Reporter: Chesnay Schepler > Assignee: TisonKun > Priority: Major > > 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. > [~Tison] Would be be interested in this issue? -- This message was sent by Atlassian Jira (v8.3.2#803003)