-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 canRemain method to TargetPoolAllocationDecider to move shards from local to remote pool for hot to warm tiering #15010
Add canRemain method to TargetPoolAllocationDecider to move shards from local to remote pool for hot to warm tiering #15010
Conversation
dce0342
to
cc33864
Compare
❌ Gradle check result for dce0342: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for cc33864: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
cc33864
to
e364d1e
Compare
❌ Gradle check result for e364d1e: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
e364d1e
to
c3a6aa1
Compare
❌ Gradle check result for c3a6aa1: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@shwetathareja thanks for your review, addressed your comments. |
local to remote pool for hot to warm tiering Signed-off-by: Neetika Singhal <neetiks@amazon.com>
99d8510
to
a6eee28
Compare
❌ Gradle check result for 99d8510: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❕ Gradle check result for a6eee28: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-15010-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c19cf88d266d15d6e8c69296cd0626099e562e38
# Push it to GitHub
git push --set-upstream origin backport/backport-15010-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x Then, create a pull request where the |
…om (opensearch-project#15010) local to remote pool for hot to warm tiering Signed-off-by: Neetika Singhal <neetiks@amazon.com> (cherry picked from commit c19cf88)
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.17 2.17
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.17
# Create a new branch
git switch --create backport/backport-15010-to-2.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c19cf88d266d15d6e8c69296cd0626099e562e38
# Push it to GitHub
git push --set-upstream origin backport/backport-15010-to-2.17
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.17 Then, create a pull request where the |
this change is also present in 2.17 |
…om (opensearch-project#15010) local to remote pool for hot to warm tiering Signed-off-by: Neetika Singhal <neetiks@amazon.com>
…om (opensearch-project#15010) local to remote pool for hot to warm tiering Signed-off-by: Neetika Singhal <neetiks@amazon.com>
…om (opensearch-project#15010) local to remote pool for hot to warm tiering Signed-off-by: Neetika Singhal <neetiks@amazon.com>
…om (opensearch-project#15010) local to remote pool for hot to warm tiering Signed-off-by: Neetika Singhal <neetiks@amazon.com>
Description
This pr adds canRemain method to TargetPoolAllocationDecider to move shards from local to remote pool for hot to warm tiering. Also, makes changes in the LocalShardsBalancer to not skip the shards tiered from hot to warm.
Related Issues
Related PR: #14891
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.