Hi NewUser,
A few questions:
- Is your "default-distributed-db-config.json" file identical on all the
nodes?
- Is your hazelcast.xml file updated to match your new setup?
- When you created the new nodes, did you delete the
"distributed-config.json" file in the database folder of the first node
that was started?
- What is the executionMode set to?
Amir.
On Sunday, May 10, 2015 at 4:37:21 PM UTC-5, NewUser wrote:
>
> Hi,
> I am using orientdb-community-2.0.5 I was able to successfully query when
> I had 2 nodes in my distributed setup but now I cannot anymore since I went
> upto 4 nodes.
> I have set autoDeploy: false and copied the databases to the database
> directory.
> I have changed the default database directory to a disk.
> I am using tcp - ip mode in hazelcast on amazon to carry out the queries.
>
> this is the error I am getting:
>
> Caused by:
> com.orientechnologies.orient.server.distributed.ODistributedException:
> Quorum 2 not reached for request (id=2 from=node1 task=tx userName=admin).
> Timeout=9015ms No server in conflict. Received:
> {node1=waiting-for-response, node4=waiting-for-response, node3=[]}
>
> at
> com.orientechnologies.orient.server.distributed.ODistributedResponseManager.manageConflicts(ODistributedResponseManager.java:576)
>
> at
> com.orientechnologies.orient.server.distributed.ODistributedResponseManager.getFinalResponse(ODistributedResponseManager.java:340)
>
> at
> com.orientechnologies.orient.server.hazelcast.OHazelcastDistributedDatabase.waitForResponse(OHazelcastDistributedDatabase.java:364)
>
> at
> com.orientechnologies.orient.server.hazelcast.OHazelcastDistributedDatabase.send2Nodes(OHazelcastDistributedDatabase.java:191)
>
> ... 10 more
>
>
> Please help!
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
