Hi Everyone. I feel like when I have OrientDB figured out something else
goes wrong. At this time, I have a 4-node installation in Azure -- two in
US East2 and two in US West -- where now the nodes in US West are logging
the following exception and the data is not replicated across regions to
those servers:
2015-04-15 01:56:10:624 WARNING [10.1.0.4]:2434 [orientdb] [3.3] Op:
> com.hazelcast.queue.impl.PollOperation@52c48276,
> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
> this:Address[10.1.0.4]:2434, target:Address[10.1.0.5]:2434, partitionId:
> 156, replicaIndex: 0, operation:
> com.hazelcast.spi.impl.WaitNotifyServiceImpl$WaitingOp, service:
> hz:impl:queueService [WaitNotifyServiceImpl$WaitingOp]
What does this mean? How do I get OrientDB to be stable when running in a
multi-node cluster? Are there any best practices? I am running OrientDB
Community v2.0.6. Here is my default distributed JSON configuration:
{
"replication": true,
"autoDeploy": true,
"hotAlignment": false,
"resyncEvery": 15,
"readQuorum": 1,
"writeQuorum": 1,
"failureAvailableNodesLessQuorum": false,
"readYourWrites": true,
"partitioning": {
"strategy": "round-robin",
"default": 0,
"partitions": [
[ "<NEW_NODE>" ]
]
},
"clusters": {
"internal": {
"replication": false
},
"index": {
"replication": false
},
"*": {
"replication": true,
"readQuorum": 1,
"writeQuorum": 1,
"failureAvailableNodesLessQuorum": false,
"readYourWrites": true,
"partitioning": {
"strategy": "round-robin",
"default": 0,
"partitions": [
[ "<NEW_NODE>" ]
]
}
}
}
}
Thank you in advance for your assistance.
Amir.
--
---
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.
