[
https://issues.apache.org/jira/browse/FLINK-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369853#comment-16369853
]
ASF GitHub Bot commented on FLINK-8660:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5530
I think this is a nice approach.
I would suggest to not split the config options between `high-availability`
and factory that is only used in *CUSTOM* mode, but use the `high-availability`
option for both. The option describes the high availability services factory,
with *NONE* and *ZOOKEEPER* as special constants/shortcuts.
Have a look at the `StateBackendLoader` class for an example of that.
https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/state/StateBackendLoader.java#L92
> Enable the user to provide custom HAServices implementation
> ------------------------------------------------------------
>
> Key: FLINK-8660
> URL: https://issues.apache.org/jira/browse/FLINK-8660
> Project: Flink
> Issue Type: Improvement
> Components: Cluster Management, Configuration, Distributed
> Coordination
> Affects Versions: 1.4.0, 1.5.0
> Reporter: Krzysztof Białek
> Priority: Major
> Fix For: 1.6.0
>
>
> At the moment Flink uses ZooKeeper as HA backend.
> The goal of this improvement is to make Flink supporting more HA backends,
> also maintained as independent projects.
> The following changes are required to achieve it:
> # Add {{HighAvailabilityServicesFactory}} interface
> # Add new option {{HighAvailabilityMode.CUSTOM}}
> # Add new configuration property {{high-availability.factoryClass}}
> # Use the factory in {{HighAvailabilityServicesUtils}} to instantiate
> {{HighAvailabilityServices}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
