Skip to content

Managing. Monitoring. Tuning.#2653

Merged
Naarcha-AWS merged 1 commit intomainfrom
manage-monitor
Feb 6, 2023
Merged

Managing. Monitoring. Tuning.#2653
Naarcha-AWS merged 1 commit intomainfrom
manage-monitor

Conversation

@Naarcha-AWS
Copy link
Contributor

@Naarcha-AWS Naarcha-AWS commented Feb 3, 2023

Signed-off-by: Naarcha-AWS naarcha@amazon.com

Description

Describe what this change achieves.

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

Checklist

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
    For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
@Naarcha-AWS Naarcha-AWS added backport 1.3 PR: Backport label for v1.3.x backport 2.0 PR: Backport label for v2.0.x backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 backport 2.3 PR: Backport label for 2.3 backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5 labels Feb 3, 2023
@Naarcha-AWS Naarcha-AWS requested a review from a team as a code owner February 3, 2023 23:51
@Naarcha-AWS Naarcha-AWS changed the title Once more... Managing, Monitoring, Tuning. Managing. Monitoring. Tuning. Feb 3, 2023
@Naarcha-AWS
Copy link
Contributor Author

Approvals for PR occurred in #2605

@Naarcha-AWS Naarcha-AWS merged commit 45834d6 into main Feb 6, 2023
@Naarcha-AWS Naarcha-AWS deleted the manage-monitor branch February 6, 2023 17:48
@opensearch-trigger-bot
Copy link
Contributor

The backport to 1.3 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-2653-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-2653-to-1.3.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.0 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.0 2.0
# Navigate to the new working tree
cd .worktrees/backport-2.0
# Create a new branch
git switch --create backport/backport-2653-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-2.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.0

Then, create a pull request where the base branch is 2.0 and the compare/head branch is backport/backport-2653-to-2.0.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.1 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.1 2.1
# Navigate to the new working tree
cd .worktrees/backport-2.1
# Create a new branch
git switch --create backport/backport-2653-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-2.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.1

Then, create a pull request where the base branch is 2.1 and the compare/head branch is backport/backport-2653-to-2.1.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.2 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.2 2.2
# Navigate to the new working tree
cd .worktrees/backport-2.2
# Create a new branch
git switch --create backport/backport-2653-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-2.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.2

Then, create a pull request where the base branch is 2.2 and the compare/head branch is backport/backport-2653-to-2.2.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.3 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.3 2.3
# Navigate to the new working tree
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-2653-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.3

Then, create a pull request where the base branch is 2.3 and the compare/head branch is backport/backport-2653-to-2.3.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.4 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.4 2.4
# Navigate to the new working tree
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-2653-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-2.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.4

Then, create a pull request where the base branch is 2.4 and the compare/head branch is backport/backport-2653-to-2.4.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.5 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.5 2.5
# Navigate to the new working tree
cd .worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-2653-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45834d6f78697fe291189c583f7d4d689faeb075
# Push it to GitHub
git push --set-upstream origin backport/backport-2653-to-2.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.5

Then, create a pull request where the base branch is 2.5 and the compare/head branch is backport/backport-2653-to-2.5.

Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
* Once more... Managing, Monitoring, Tuning. (#2653)

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)

* Delete cluster-manager-task-throttling.md
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
* Once more... Managing, Monitoring, Tuning. (#2653)

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)

* Delete api.md

* Delete cluster-manager-task-throttling.md
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Naarcha-AWS added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
(cherry picked from commit 45834d6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 1.3 PR: Backport label for v1.3.x backport 2.0 PR: Backport label for v2.0.x backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 backport 2.3 PR: Backport label for 2.3 backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants