Skip to content
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

Merged

Conversation

neetikasinghal
Copy link
Contributor

@neetikasinghal neetikasinghal commented Jul 29, 2024

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

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

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.

Copy link
Contributor

❌ 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?

Copy link
Contributor

❌ 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?

@neetikasinghal neetikasinghal force-pushed the tiering-allocation-2.0 branch from cc33864 to e364d1e Compare July 29, 2024 22:06
Copy link
Contributor

❌ 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?

@neetikasinghal
Copy link
Contributor Author

neetikasinghal commented Jul 29, 2024

❌ 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?

@neetikasinghal neetikasinghal force-pushed the tiering-allocation-2.0 branch from e364d1e to c3a6aa1 Compare July 29, 2024 23:54
Copy link
Contributor

❌ 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?

@neetikasinghal
Copy link
Contributor Author

Thanks @neetikasinghal for the changes. Left some comments.

@shwetathareja thanks for your review, addressed your comments.

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
Copy link
Contributor

github-actions bot commented Sep 3, 2024

❌ 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?

Copy link
Contributor

github-actions bot commented Sep 3, 2024

❕ 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.

@jed326 jed326 merged commit c19cf88 into opensearch-project:main Sep 3, 2024
34 of 35 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

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 base branch is 2.x and the compare/head branch is backport/backport-15010-to-2.x.

neetikasinghal added a commit to neetikasinghal/OpenSearch that referenced this pull request Sep 3, 2024
…om (opensearch-project#15010)

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
(cherry picked from commit c19cf88)
jed326 pushed a commit that referenced this pull request Sep 3, 2024
…om (#15010) (#15628)

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
(cherry picked from commit c19cf88)
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.17 failed:

The process '/usr/bin/git' failed with exit code 128

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 base branch is 2.17 and the compare/head branch is backport/backport-15010-to-2.17.

@neetikasinghal
Copy link
Contributor Author

this change is also present in 2.17

@neetikasinghal neetikasinghal deleted the tiering-allocation-2.0 branch September 4, 2024 21:29
akolarkunnu pushed a commit to akolarkunnu/OpenSearch that referenced this pull request Sep 10, 2024
…om (opensearch-project#15010)

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
dk2k pushed a commit to dk2k/OpenSearch that referenced this pull request Oct 16, 2024
…om (opensearch-project#15010)

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
dk2k pushed a commit to dk2k/OpenSearch that referenced this pull request Oct 17, 2024
…om (opensearch-project#15010)

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
dk2k pushed a commit to dk2k/OpenSearch that referenced this pull request Oct 21, 2024
…om (opensearch-project#15010)

local to remote pool for hot to warm tiering

Signed-off-by: Neetika Singhal <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants