-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Closed
Labels
:Distributed/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)All issues relating to the decision making around placing a shard (both master logic & on the nodes)>enhancementSupportabilityImprove our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Team:DistributedMeta label for distributed team.Meta label for distributed team.stalled
Description
Description
👋 howdy, team!
Would you kindly consider adding in the index name to Cluster Pending Tasks for shard-failed (ballpark code) similar as is done for shard-started (code)?
Currently emitted examples where shard-started is informative but shard-failed is not:
{
"tasks": [
{
"executing": false,
"insert_order": 5862,
"priority": "HIGH",
- "source": "shard-failed",
"time_in_queue": "201ms",
"time_in_queue_millis": 201
},
{
"executing": false,
"insert_order": 5789,
"priority": "URGENT",
+ "source": "shard-started StartedShardEntry{shardId [[MY_INDEX_NAME][0]], allocationId [SOME_UUID], primary term [4], message [after peer recovery]}",
"time_in_queue": "1.1m",
"time_in_queue_millis": 71104
}
]
}Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Distributed/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)All issues relating to the decision making around placing a shard (both master logic & on the nodes)>enhancementSupportabilityImprove our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Team:DistributedMeta label for distributed team.Meta label for distributed team.stalled