Skip to content

Commit c5b0360

Browse files
Shard started reroute high priority (#137306)
* Shard started reroute high priority We executed shard started at urgent priority, but the subsequent reroute were at normal priority, causing subsequent recoveries to possibly come after other less important actions. Now do the reroute at high priority.
1 parent 6b2c55a commit c5b0360

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

docs/changelog/137306.yaml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
pr: 137306
2+
summary: Shard started reroute high priority
3+
area: Allocation
4+
type: enhancement
5+
issues: []

server/src/main/java/org/elasticsearch/cluster/action/shard/ShardStateAction.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -829,7 +829,7 @@ private static boolean assertStartedIndicesHaveCompleteTimestampRanges(ClusterSt
829829
public void clusterStatePublished(ClusterState newClusterState) {
830830
rerouteService.reroute(
831831
"reroute after starting shards",
832-
Priority.NORMAL,
832+
Priority.HIGH,
833833
ActionListener.wrap(
834834
r -> logger.trace("reroute after starting shards succeeded"),
835835
e -> logger.debug("reroute after starting shards failed", e)

0 commit comments

Comments
 (0)