-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
log flooding when using retry_join #599
Comments
Thanks for the report! Can you show the command you used to invoke Nomad? The serf consensus / retry is much more aggressive than 30s delay so I suspect that one of your CLI flags was not passed in correctly. |
@charlieok I am not using special command , see below nomad agent -config /etc/nomad.d/server.hcl server.hcl
|
I've seen this too myself before |
I am trying to reproduce this now. |
Cool , wait for next release . |
@yikaus We just released 0.2.3 which had this fix! |
Just tried new release , it is fixed . Thanks |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomd v.0.2.2
When applied below configuration to manually join a cluster , the log file get flooded until other nodes are available
Enable the server
server {
enabled = true
bootstrap_expect = 3
retry_join = ["192.169.0.20","192.168.0.21"]
}
However it showing retrying in 30s , but actually not having any delay
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
2015/12/17 22:11:27 [WARN] agent: Join failed: dial tcp 192.168.0.20:4648: getsockopt: connection refused, retrying in 30s
The text was updated successfully, but these errors were encountered: