-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Add CCS based reindex in doc page #117154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
8f66c41
69985f7
e058651
34a6708
6ae57e0
670899d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -98,6 +98,9 @@ privilege for the source data stream, index, or alias. | |||||||||||||||||||
in the `reindex.remote.whitelist` setting of `elasticsearch.yml`. See | ||||||||||||||||||||
<<reindex-from-remote>>. | ||||||||||||||||||||
|
||||||||||||||||||||
* If ccs-based reindexing from a remote cluster, you must add the remote cluster setting. See | ||||||||||||||||||||
<<add-remote-clusters>>. | ||||||||||||||||||||
|
||||||||||||||||||||
* Automatic data stream creation requires a matching index template with data | ||||||||||||||||||||
stream enabled. See <<set-up-a-data-stream>>. | ||||||||||||||||||||
|
||||||||||||||||||||
|
@@ -1125,6 +1128,30 @@ POST _reindex | |||||||||||||||||||
// TEST[s/otherhost:9200/\${host}/] | ||||||||||||||||||||
// TEST[s/\.\.\.,/"username": "test_admin", "password": "x-pack-test-password",/] | ||||||||||||||||||||
|
||||||||||||||||||||
[[ccs-based-reindex-from-remote]] | ||||||||||||||||||||
==== ccs based reindex from remote | ||||||||||||||||||||
|
||||||||||||||||||||
Reindex supports Cross-cluster search (<<modules-cross-cluster-search,{ccs}>>) based reindexing from a remote Elasticsearch cluster: | ||||||||||||||||||||
Comment on lines
+1131
to
+1134
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Since a section named reindex-from-remote already exists, won't it be difficult to understand what the difference is with |
||||||||||||||||||||
|
||||||||||||||||||||
[source,console] | ||||||||||||||||||||
-------------------------------------------------- | ||||||||||||||||||||
POST _reindex | ||||||||||||||||||||
{ | ||||||||||||||||||||
"source": { | ||||||||||||||||||||
"index": "cluster_one:my-index-000001" | ||||||||||||||||||||
}, | ||||||||||||||||||||
"dest": { | ||||||||||||||||||||
"index": "my-new-index-000001" | ||||||||||||||||||||
} | ||||||||||||||||||||
} | ||||||||||||||||||||
-------------------------------------------------- | ||||||||||||||||||||
// TEST[setup:my_index_big] | ||||||||||||||||||||
|
||||||||||||||||||||
The `index` parameter must be specified with the remote cluster name and the index name, separated by | ||||||||||||||||||||
a colon (e.g., cluster_one:my-index-000001). | ||||||||||||||||||||
|
||||||||||||||||||||
NOTE: Reindexing requires that the remote cluster be configured on the local cluster. | ||||||||||||||||||||
|
||||||||||||||||||||
[[reindex-ssl]] | ||||||||||||||||||||
===== Configuring SSL parameters | ||||||||||||||||||||
|
||||||||||||||||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it looks like a condition for performing an existing reindex, I think it would be better to give it a different name to avoid confusing users.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I agree that we should keep the terminology to "ccs-based reindexing" to distinguish this from the pre-existing functionality of reindexing from a remote cluster.