GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/3622
[FLINK-6136] Separate EmbeddedHaServices and StandaloneHaServices
This PR introduces a standalone high availability services implementation
which can be used
in a distributed setting with no HA guarantees. Additionally, it introduces
a common base
class which is also used by the EmbeddedHaServices. This base class
instantiates the
standalone variants of the checkpoint recovery factory, submitted job
graphs store, running
jobs registry and blob store.
The StandaloneHaServices are instantiated with a fixed address for the Job-
and
ResourceManager. This address and the HighAvailability.DEFAULT_LEADER_ID is
returned by
the corresponding LeaderRetrievalServices when being started.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink separateNonHaServices
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3622.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3622
----
commit 3f85d6b3ef41df4e795bb3ef5beecca49606caba
Author: Till Rohrmann <[email protected]>
Date: 2017-03-21T14:10:15Z
[FLINK-6136] Separate EmbeddedHaServices and StandaloneHaServices
This PR introduces a standalone high availability services implementation
which can be used
in a distributed setting with no HA guarantees. Additionally, it introduces
a common base
class which is also used by the EmbeddedHaServices. This base class
instantiates the
standalone variants of the checkpoint recovery factory, submitted job
graphs store, running
jobs registry and blob store.
The StandaloneHaServices are instantiated with a fixed address for the Job-
and
ResourceManager. This address and the HighAvailability.DEFAULT_LEADER_ID is
returned by
the corresponding LeaderRetrievalServices when being started.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
