hashicorp / hashicorp/raft

Quiet a server that's no longer in the cluster

Open
#174 2 comments 3 reactions 0 assignees View on GitHub
enhancement thinking
Dominant language
Go
Stars
9.1k
Forks
1.1k
Avg merge
3h 27m
Merged PRs (30d)
2

Description

If a server leaves a configuration it may not actually get the log entry replicated that removes it, so it'll try to start elections. The rest of the cluster will ignore it, but if we give it feedback to shut up it will be less of a noisy process.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating the election behavior for a server that has left the configuration, then determine how the remaining cluster can signal that server to stop campaigning; done means the removed server no longer starts noisy elections.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.