Skip to content
This repository has been archived by the owner on Nov 18, 2017. It is now read-only.

golang-custom-raft: maximum_lag_on_failover doesn't work as it should #46

Open
doodles526 opened this issue Nov 27, 2016 · 0 comments
Open

golang-custom-raft: maximum_lag_on_failover doesn't work as it should #46

doodles526 opened this issue Nov 27, 2016 · 0 comments
Labels
bug golang-custom-raft in progress

Comments

@doodles526
Copy link
Contributor

maximum_lag_on_failover incorrectly tries to query an existing leader for the WAL position. Problem is, the time which maximum_lag_on_failover should be checked - a leader wouldn't exist. Solution would be to implement historic information on members
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug golang-custom-raft in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@doodles526