Skip to content
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.

Sign up for GitHub

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

Excessive heartbeater logging of "connection refused" on cluster node stop #1896

Closed
grisha opened this issue Mar 9, 2015 · 2 comments · Fixed by #2416
Closed

Excessive heartbeater logging of "connection refused" on cluster node stop #1896

grisha opened this issue Mar 9, 2015 · 2 comments · Fixed by #2416
Assignees
@jwilder

Comments

@grisha
Copy link

grisha commented Mar 9, 2015

Same 3 node set up as described in #1882. If I stop one of the nodes, the other two start spewing "connection refused" to the log at the rate of several per-second, which seems to me like a potential problem (tried setting raft-tracing to false in config, but that doesn't seem to help):

[raft]  2015/03/09 23:04:46 heartbeater: error: Get http://echo05:8086/raft/heartbeat?commitIndex=1392&leaderID=1&term=5: dial tcp 192.168.122.105:8086: connection refused
[raft]  2015/03/09 23:04:46 heartbeater: error: Get http://echo05:8086/raft/heartbeat?commitIndex=1392&leaderID=1&term=5: dial tcp 192.168.122.105:8086: connection refused
[raft]  2015/03/09 23:04:46 heartbeater: error: Get http://echo05:8086/raft/heartbeat?commitIndex=1392&leaderID=1&term=5: dial tcp 192.168.122.105:8086: connection refused
[raft]  2015/03/09 23:04:46 heartbeater: error: Get http://echo05:8086/raft/heartbeat?commitIndex=1392&leaderID=1&term=5: dial tcp 192.168.122.105:8086: connection refused
[raft]  2015/03/09 23:04:46 heartbeater: error: Get http://echo05:8086/raft/heartbeat?commitIndex=1392&leaderID=1&term=5: dial tcp 192.168.122.105:8086: connection refused
[raft]  2015/03/09 23:04:46 heartbeater: error: Get http://echo05:8086/raft/heartbeat?commitIndex=1392&leaderID=1&term=5: dial tcp 192.168.122.105:8086: connection refused
@beckettsean
Copy link
Contributor

Fixed in later RCs.

@jwilder
Copy link
Contributor

jwilder commented Apr 23, 2015

Still an issue in RC27. Re-opening.

@jwilder jwilder reopened this Apr 23, 2015
jwilder added a commit that referenced this issue Apr 24, 2015
@jwilder
Log heartbeat error once every 15s
174afb5 
Prevents logs from getting flooded with a message every second when
a broker node is down.

Fixes #1896
@jwilder jwilder mentioned this issue Apr 24, 2015
Merged
@jwilder jwilder self-assigned this Apr 24, 2015
mark-rushakoff pushed a commit that referenced this issue Jan 11, 2019
@stuartcarnie
Merge pull request #1896 from influxdata/sgc-group-panic
b589c42 
Fix panic when read request results in empty an group
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jwilder jwilder

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix excessive heartbeater logging of "connection refused" on cluster node stop influxdata/influxdb
3 participants
@jwilder @grisha @beckettsean