Skip to content

Conversation

@Tim-Brooks
Copy link
Contributor

This PR opens a proof of concept for CCR recovery. It is pretty basic
without much resiliency to failures. It pulls in the work from #35719,
#37733 and #37562 and integrates it. There is a single test added to
ensure that files are being recovered when the follower falls behind.

@Tim-Brooks
Copy link
Contributor Author

As I mention in the description this is kind of rough. There is no retry or error handling. Additionally, there are shortcomings like (I think) we need to retain the original follower request as its options need to be retained for recovery bootstrapping.

@colings86 colings86 added the :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features label Jan 24, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

martijnvg and others added 8 commits January 24, 2019 10:31
…xception with

a special header instead. MissingHistoryOperationsException couldn't be used
because it ended up getting serialized in certain cases and this exception
was then not handled correctly.
a different place where it never gets serialized and there
covert it into the wrapper exception.
@ywelsch ywelsch closed this Jan 29, 2019
@Tim-Brooks Tim-Brooks deleted the ccr_recovery_poc branch December 18, 2019 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed Indexing/CCR Issues around the Cross Cluster State Replication features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants