-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Change priority for scheduling reroute during timeout #16445
base: main
Are you sure you want to change the base?
Changes from 1 commit
5e83a92
6a448d0
825a983
5368e7f
2ba604d
6e3b4d0
7329867
33ffefb
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 |
---|---|---|
|
@@ -308,8 +308,8 @@ public void onComplete() { | |
logger.trace("scheduling reroute after existing shards allocator timed out for primary shards"); | ||
assert rerouteService != null; | ||
rerouteService.reroute( | ||
"reroute after existing shards allocator timed out", | ||
Priority.HIGH, | ||
"reroute after existing shards allocator [P] timed out", | ||
Priority.NORMAL, | ||
ActionListener.wrap( | ||
r -> logger.trace("reroute after existing shards allocator timed out completed"), | ||
e -> logger.debug("reroute after existing shards allocator timed out failed", e) | ||
|
@@ -343,8 +343,8 @@ public void onComplete() { | |
logger.trace("scheduling reroute after existing shards allocator timed out for replica shards"); | ||
assert rerouteService != null; | ||
rerouteService.reroute( | ||
"reroute after existing shards allocator timed out", | ||
Priority.HIGH, | ||
"reroute after existing shards allocator [R] timed out", | ||
Priority.NORMAL, | ||
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. Should we have a separate priority for primary vs replica? 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. NORMAL also seems right for PSA. But during genuine issues in the cluster which can be identified with appropriate monitoring, we might need to raise it to HIGH. I will update the PR with a similar setting for ESA similar to BSA to raise reroute priority. Wdyt? |
||
ActionListener.wrap( | ||
r -> logger.trace("reroute after existing shards allocator timed out completed"), | ||
e -> logger.debug("reroute after existing shards allocator timed out failed", e) | ||
|
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.
we should add a changelog as we are changing the default priority from HIGH to NORMAL