Skip to content

Conversation

@Tim-Brooks
Copy link
Contributor

Currently, the CcrRepositoryManger only listens for settings updates
and installs new repositories. It does not install the repositories that
are in the initial settings. This commit, modifies the manager to
install the initial repositories. Additionally, it modifies the ccr
integration test to configure the remote leader node at startup, instead
of using a settings update.

Currently, the CcrRepositoryManger only listens for settings updates
and installs new repositories. It does not install the repositories that
are in the initial settings. This commit, modifies the manager to
install the initial repositories. Additionally, it modifies the ccr
integration test to configure the remote leader node at startup, instead
of using a settings update.
@Tim-Brooks Tim-Brooks added >non-issue :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features backport v6.7.0 labels Dec 20, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@Tim-Brooks Tim-Brooks merged commit 7d3d12f into elastic:6.x Dec 21, 2018
@Tim-Brooks Tim-Brooks deleted the backport_init_startup_repos branch December 18, 2019 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features >non-issue v6.7.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants