Better handling of cluster-level shard routing allocation in Elastic cookbooks
Open, HighPublic
Actions

Assigned To

None

Authored By

	bking
	Dec 12 2022, 2:53 PM

Description

Our rolling operation cookbook sets cluster-level shard allocation to primaries only, which speeds up operations. However, if the cookbook fails, this setting is never reverted.

This may lead to alerts for unassigned shards, as seen in T324939 .

Creating this ticket to:

Update rolling operation cookbook to re-enable cluster-level shard allocation for all shards (not just primaries) after a failure.

Update rolling operation cookbook to use persistent cluster settings in place of the deprecated transient settings

Related Objects

Mentioned In: T324939: Multiple unassigned shards on the Elasticsearch relforge cluster
Mentioned Here: T324939: Multiple unassigned shards on the Elasticsearch relforge cluster

Event Timeline

bking created this task.Dec 12 2022, 2:53 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 12 2022, 2:53 PM

bking mentioned this in T324939: Multiple unassigned shards on the Elasticsearch relforge cluster.Dec 12 2022, 2:56 PM

MPhamWMF triaged this task as High priority.Dec 12 2022, 4:51 PM

MPhamWMF moved this task from needs triage to Ops / SRE on the Discovery-Search board.

Gehel edited projects, added Discovery-Search (Current work); removed Discovery-Search.Dec 16 2022, 8:18 AM

Gehel edited projects, added Discovery-Search; removed Discovery-Search (Current work).Jan 23 2023, 4:30 PM

Better handling of cluster-level shard routing allocation in Elastic cookbooksOpen, HighPublicActions

Description

Related Objects

Event Timeline

Better handling of cluster-level shard routing allocation in Elastic cookbooks
Open, HighPublic
Actions