-
Notifications
You must be signed in to change notification settings - Fork 504
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
Add documentation for remote store migration #7121
Add documentation for remote store migration #7121
Conversation
Signed-off-by: Gaurav Bafna <[email protected]>
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.
Looks good from the technical standpoint. Approving.
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Show resolved
Hide resolved
Co-authored-by: Bhumika Saini <[email protected]> Signed-off-by: Gaurav Bafna <[email protected]>
Signed-off-by: Gaurav Bafna <[email protected]>
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Show resolved
Hide resolved
Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Gaurav Bafna <[email protected]>
PUT "/_cluster/settings?pretty" | ||
{ | ||
"persistent": { | ||
"remote_store.compatibility_mode": null, |
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.
I tried running this but it is failing currently (see opensearch-project/OpenSearch#13634). Maybe for 2.14 we can add a step to explicitly set this to strict
? In 2.15 we can update the docs once we have the bugfix in.
Signed-off-by: Gaurav Bafna <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
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.
@gbbafna @Naarcha-AWS Please see my comments and changes and let me know if you have any questions. Thanks!
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
} | ||
``` | ||
|
||
1. Set the `remote_store.compatibility_mode` setting to `mixed` to allow remote-store backed nodes to join the cluster. Then, set `migration.direction` to `remote_store`, which makes new indexes are allocated to remote backed data nodes. The following example updates the aforementioned setting using the Cluster settings API: |
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.
First sentence: "remote-store backed" => "remote-backed storage"? Otherwise, "remote-store-backed"
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/remote-store/migrating-to-remote.md
Outdated
Show resolved
Hide resolved
| Field | Data type | Description | | ||
| :--- |:----------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| remote_store.compatibility_mode | String | Defaults to`strict` mode where it only allows either non-remote or remote nodes depending upon the initial cluster type. When set to `mixed`, it allows remote and non-remote nodes to join the cluster. | | | ||
| migration.direction | String | Defaults to `none` . `remote_store` direction creates new shards only on remote store backed nodes. | |
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.
A direction cannot technically create anything. Either "remote-backed storage nodes" or "remote-store-backed nodes".
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
| Field | Data type | Description | | ||
| :--- |:----------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| `remote_store.compatibility_mode` | String | Defaults to `strict` mode, which only allows either non-remote or remote nodes, depending upon the initial cluster type. When set to `mixed`, it allows remote and non-remote nodes to join the cluster. | | | ||
| `migration.direction` | String | Creates new shards only on remote-backed storage nodes. Default is `None`. | |
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.
| `migration.direction` | String | Creates new shards only on remote-backed storage nodes. Default is `None`. | | |
| `migration.direction` | String | Creates new shards only on remote-backed storage nodes. Default is `None`. | |
Description
Issues Resolved
resolves #7120
List any issues this PR will resolve, e.g. Closes [...].
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.