Make chef-backend more reliable
Open
Nobody has claimed this yet.
Status: Consider for next release
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
- route to all ES nodes from chef-server instead of only the leaderl node.
- remove the elasticsearch health check from leaderl or otherwise exclude it from the leader eligibility status
- remove the etcd health check from leaderl or otherwise exclude it from the leader eligibility status.
- (maybe) enable etcd request retries by default
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 locating the chef-backend paths for Elasticsearch routing and leader eligibility. Trace how the Elasticsearch and etcd health checks affect leader status, then review the existing etcd request behavior. Done means routing reaches all Elasticsearch nodes, the specified health checks no longer incorrectly determine eligibility, and the retry change is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, erlang
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100