mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
52afaf2060
When a data stream is being auto followed then a rollover in a local cluster can break auto following, if the local cluster performs a rollover then it creates a new write index and if then later the remote cluster rolls over as well then that new write index can't be replicated, because it has the same name as in the write index in the local cluster, which was created earlier. If a data stream is managed by ccr, then the local cluster should not do a rollover for those data streams. The data stream should be rolled over in the remote cluster and that change should replicate to the local cluster. Performing a rollover in the local cluster is an operation that the data stream support in ccr should perform. To protect against rolling over a replicated data stream, this PR adds a replicate field to DataStream class. The rollover api will fail with an error in case a data stream is being rolled over and the targeted data stream is a replicated data stream. When the put follow api creates a data stream in the local cluster then the replicate flag is set to true. There should be a way to turn a replicated data stream into a regular data stream when for example during disaster recovery. The newly added api in this pr (promote data stream api) is doing that. After a replicated data stream is promoted to a regular data stream then the local data stream can be rolled over, so that the new write index is no longer a follower index. Also if the put follow api is attempting to update this data stream (for example to attempt to resume auto following) then that with fail, because the data stream is no longer a replicated data stream. Today with time based indices behind an alias, the is_write_index property isn't replicated from remote cluster to the local cluster, so when attempting to rollover the alias in the local cluster the rollover fails, because the alias doesn't have a write index. The added replicated field in the DataStream class and added validation achieve the same kind of protection, but in a more robust way. A followup from #61993.
38 lines
1.1 KiB
Text
38 lines
1.1 KiB
Text
[role="xpack"]
|
|
[[promote-data-stream-api]]
|
|
=== Promote Data Stream API
|
|
++++
|
|
<titleabbrev>Promote data stream api</titleabbrev>
|
|
++++
|
|
|
|
The purpose of the promote data stream api is to turn
|
|
a data stream that is replicated by CCR into a regular
|
|
data stream.
|
|
|
|
Via CCR Auto Following, a data stream from a remote cluster
|
|
can be replicated to the local cluster. These data streams
|
|
can't be rolled over in the local cluster. Only if the upstream
|
|
data stream rolls over then these replicated data streams roll
|
|
over as well. In the event that the remote cluster is no longer
|
|
available, the data stream in the local cluster can be promoted
|
|
to a regular data stream, which allows these data streams to
|
|
be rolled over in the local cluster.
|
|
|
|
[source,console]
|
|
----
|
|
POST /_data_stream/_promote/my-data-stream
|
|
----
|
|
// TEST[catch:missing]
|
|
|
|
[[promote-data-stream-api-request]]
|
|
==== {api-request-title}
|
|
|
|
`POST /_data_stream/_promote/<data-stream>`
|
|
|
|
|
|
[[promote-data-stream-api-path-params]]
|
|
==== {api-path-parms-title}
|
|
|
|
`<data-stream>`::
|
|
(Required, string)
|
|
The name of the data stream to promote.
|