opensearch-project / opensearch-project/OpenSearch
[Zone Decommission] Update peerFinderInterval with backoff policy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.7k
- Forks
- 3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 108
Description
As per comment in #4590, we expect a back off policy attached while updating the findPeerInterval for decommissioned nodes.
Currently, to control the discovery of decommissioned nodes to avoid throttling issues, we set the findPeerInterval to 120sec. Now for cases when the user has accidentally decommissioned a zone and now wants to recommission it back, the user might need to wait for 120 sec in the worst case. If we could attach a exponential back off policy to plateau to 120 sec rather than directly to 120 sec would be really helpful for such cases.
The scope of this issue is limited to attaching a exponential backoff policy while controlling the discovery of decommissioned nodes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the decommissioned-node discovery logic that controls findPeerInterval, along with the discussion in pull request #4590. Confirm how the interval currently becomes 120 seconds and define the exponential backoff behavior, including its 120-second plateau. Done means recommissioning can retry sooner while discovery remains protected from throttling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100