Failure stores cannot be replicated in CCR #126356
Labels
:Data Management/Data streams
Data streams and their lifecycles
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>enhancement
Team:Data Management
Meta label for data/management team
Team:Distributed Indexing
Meta label for Distributed Indexing team
We currently filter failure store indices out from being considered for auto follow logic when processing data streams (see #126355). This is because a write index must always be present on a data stream. If a failure index is the only index from a cluster that is replicated (i.e. no other backing indices are replicated), the resulting follower data stream is not guaranteed to satisfy this invariant. Even if all indices are replicated, the construction of the data stream to hold them is done as part of the follow operation. If follow operations are done in arbitrary order and are subject to independent failure, we can't guarantee that a data stream will always have a write index in its backing index set.
The text was updated successfully, but these errors were encountered: