-
Notifications
You must be signed in to change notification settings - Fork 872
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
Timeout on waiting for synchronous responses From other nodes #8742
Comments
+1 got exactly the same problem with odb 3.3.18 here |
+1. Same issue in odb 3.0.18. Retry loop does not solve the issue either. Occurs even with high timeouts up to 14 s 2019-08-03 13:00:38:619 WARNI [orientdb-0] Timeout (40001ms) on waiting for synchronous responses from nodes=[orientdb-2, orientdb-1] responsesSoFar=[orientdb-1] request=(id=0.20026 task=upd_db_status) [ODistributedDatabaseImpl] |
I am getting the same exception when starting a node in a cluster (OrientDB 3.0.23): Timeout (63696ms) on waiting for synchronous responses from nodes=[node_4] responsesSoFar=[] request=(id=1.4 task=copy_db_chunk) [ODistributedDatabaseImpl]Exception See also #8994 |
Same on 3.0.30: |
Hei All; I'm using Orientdb 3.0.28 with 2 cluster and facing similar issue. It prevents writing and our apps throwing Out of Memory error and stops finally. My default-distributed-db-config.json: { Any update on it? |
OrientDB Version: 3.0.13
Java Version: 8
OS: Debian 9
Expected behavior
We are using orientDB in distributed mode. If we create/update edges on any of the masters it should get persisted /updated without any exceptions or warnings.
Cluster size: 3 (master, master, replica)
Actual behavior
when we create/update edges, we get following error:
2019-01-28 16:58:20:877 WARNI [node1] Timeout (1213ms) on waiting for synchronous responses from nodes=[node2, node1, node3] responsesSoFar=[node1, node1] request=(id=0.116757 task=TxPhase1) [ODistributedDatabaseImpl]
Steps to reproduce
Any Insert statement on the master is causing this issue.
The text was updated successfully, but these errors were encountered: