long latency node join 5 nodes cluster failure
See original GitHub issueI tried to join a node to my existing cluster from a different region which has 100ms latency. The API server of the new node keeps restarting.
But, if I join another empty one node cluster in the same place with the 5 nodes cluster. It could work.
It seems the API server waited too short time before the deadline is reached?
Feb 19 05:01:15 de1 microk8s.daemon-apiserver[13747]: W0219 05:01:15.220327 13747 authentication.go:519] AnonymousAuth is not allowed with the AlwaysAllow authorizer. Resetting AnonymousAuth to false. You should use a different authorizer
Feb 19 05:02:15 de1 microk8s.daemon-apiserver[13747]: Error: context deadline exceeded
Feb 19 05:02:15 de1 systemd[1]: snap.microk8s.daemon-apiserver.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 05:02:15 de1 systemd[1]: snap.microk8s.daemon-apiserver.service: Failed with result 'exit-code'.
Feb 19 05:02:15 de1 systemd[1]: snap.microk8s.daemon-apiserver.service: Scheduled restart job, restart counter is at 10.
Issue Analytics
- State:
- Created 3 years ago
- Comments:21
Top Results From Across the Web
long latency node join 5 nodes cluster failure · Issue #2033
I tried to join a node to my existing cluster from a different region which has 100ms latency. The API server of the...
Read more >Tuning Failover Cluster Network Thresholds
Delay – This defines the frequency at which cluster heartbeats are sent between nodes. The delay is the number of seconds before the...
Read more >Cluster fault detection | Elasticsearch Guide [8.5]
If a node takes too long to process a cluster state update, it can be harmful to the cluster. The master will remove...
Read more >Data-Driven Packet Loss Estimation for Node Healthy Sensing ...
If one detects a failure, it will mark this node in its own member state table and try to gossip it to the...
Read more >Integrated Storage | Vault
A 3 node cluster with a large amount of data that's at a failure tolerance of 1. · Another 3 new nodes then...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Aaa you’re right. It does a
kubectl get no
.You can actually forcefully remove it from dqlite with this command.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.