Documentation of "druid.coordinator.load.timeout" is unclear
Open
Area - Documentation
Area - Segment Balancing/Coordination
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
Currently, it says:
> The timeout duration for when the Coordinator assigns a segment to a Historical node.
But doesn't what happens next. Historical node is considered unresponsive and no more assignments are done to it? A request is sent to cancel the assignment? A segment is assigned to a different Historical node?
Contributor guide
Research direction
Locate the documentation entry for druid.coordinator.load.timeout and trace the Coordinator's assignment behavior after the timeout. Confirm whether the Historical node is considered unresponsive, the assignment is cancelled, or the segment is reassigned, then update the documentation to describe the observed behavior clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100