Skip to content

Commit

Permalink
chore(server): set DefaultRemoveDelay to 30mins
Browse files Browse the repository at this point in the history
Its value was 5s before, which could remove the node insanely fast.
  • Loading branch information
yichengq committed Jun 6, 2014
1 parent 79c650d commit ed58193
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions Documentation/design/standbys.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@ If there are not enough peers to meet the active size, standbys will send join r
If there are more peers than the target active size then peers are removed by the leader and will become standbys.

The remove delay specifies how long the cluster should wait before removing a dead peer.
By default this is 5 seconds.
If a peer is inactive for 5 seconds then the peer is removed.
By default this is 30 minutes.
If a peer is inactive for 30 minutes then the peer is removed.

The standby sync interval specifies the synchronization interval of standbys with the cluster.
By default this is 5 seconds.
Expand Down
2 changes: 1 addition & 1 deletion server/cluster_config.go
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ const (
MinActiveSize = 3

// DefaultRemoveDelay is the default elapsed time before removal.
DefaultRemoveDelay = float64((5 * time.Second) / time.Second)
DefaultRemoveDelay = float64((30 * time.Minute) / time.Second)

// MinRemoveDelay is the minimum remove delay allowed.
MinRemoveDelay = float64((2 * time.Second) / time.Second)
Expand Down

0 comments on commit ed58193

Please sign in to comment.