Skip to content

/ postgres_cluster

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Raftable client always tries to connect dead node. #13

Closed
kelvich opened this issue Aug 11, 2016 · 0 comments
Closed

Raftable client always tries to connect dead node. #13

kelvich opened this issue Aug 11, 2016 · 0 comments
Milestone
1.0.0

Comments

@kelvich
Copy link
Collaborator

@kelvich kelvich commented Aug 11, 2016

Setup cluster of 3 nodes, pgbench -i, kill first one, pgbench of node2 (or just commit rw tx in connection):

WARNING:  raftable client: trying [0] localhost:6543
WARNING:  raftable client: connect timed out
WARNING:  raftable client: could not connect
WARNING:  raftable client: connect_leader() failed
WARNING:  raftable query failed after 452 ms
progress: 1.0 s, 270.0 tps, lat 3.688 ms stddev 27.804
WARNING:  raftable client: trying [2] localhost:6545
@kelvich kelvich modified the milestone: 1.0.0 Sep 8, 2016
@kelvich kelvich closed this Oct 14, 2016
kelvich added a commit that referenced this issue Oct 17, 2016
@kelvich
run recovery tests at travis #13
Loading status checks…
9b2e24b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0.0
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@kelvich
You can’t perform that action at this time.