-
Notifications
You must be signed in to change notification settings - Fork 1k
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
cluster couchdb unstable (fabric_worker_timeout) #4790
Comments
It seems like nodes are having a hard time staying connected. Is networking connectivity between cluster nodes fairly stable? Try to upgrade to the latest Apache CouchDB as there is periodic forced re-connection module. The setting is There is also Hint: you can use three backward ticks to enclose logs so they are rendered as pre-formatted text. |
Hi Nickva, |
Not sure I can explain that from the logs. It seems like other nodes also have connectivity issues and timeouts. I see some disconnects between 440 <-> 410:
See if perhaps you'd also add an ioq bypass for If you're running in a kube environment check that each of the containers have the same and enough CPU and disk IO resources/bandwidth available. |
We have cached the same issue on v3.3.3
But during troubleshooting when the issue was present I sent On the other two nodes in the cluster, I can see error messages like "fabric_worker_timeout open_doc" and no messages like "Node not responding". Also on the two nodes CPU load increased to 100%. I am sure network connectivity is present between CouchDB nodes. Also
|
Hi everyone.
I present to you a problem that we are randomly encountering.
this is a 3 node couchdb cluster. one of them (always the same) apparently for no reason, signals countless "fabric_worker_timeout" and is finally excluded from the cluster until the restart.
Below are the logs and configuration.
thanks to everyone who wants to contribute
configuration:
3 node cluster:
host440 --> S.O. Ubuntu 18.04.5 LTS (Bionic Beaver) (kernel 5.4.0-1040-azure)
host430 --> S.O. Ubuntu 18.04.5 LTS (Bionic Beaver) (kernel 5.4.0-1064-azure)
host410 --> S.O. Ubuntu 18.04.4 LTS (Bionic Beaver) (kernel 5.4.0-1095-azure) (crashed node)
The text was updated successfully, but these errors were encountered: