Using default distributed configuration [1] with 1.7 snapshot [2]. I have 3
nodes i1, i2, and i3 all
running orientdb-community-1.7-20140409.215941-107-distribution.tar.gz.
Basic Setup
Up: i1, i2, i3
create class Data extends V
create property Data.name string
create index Data_name on Data (name) unique
Expecting class, property, and index to be created in all nodes. This
happens as expected.
Scenario
Up: i1, i2, i3
create vertex Data set name = 'foo'
Expecting all nodes to receive new node (happens as expected).
Now node i3 is take down.
Up: i1, i2
create vertex Data set name = 'bar'
Expecting i1, i2 to see new node (happens as expected).
Bring node i3 up.
Expecting i3 to synchronize and see 'bar', BUT this never happens. The only
way I've gotten 'bar' to show up on i3 is to completely delete the
databases from i3 and restart it (with a 50/50 chance that it will properly
sync the database to it).
Am I expecting the right behavior? Is this a bug? Or am I misunderstanding
the distributed architecture and routing?
Thanks in advance, this is a really neat database.
Caleb
[1] Default default-distributed-db-config.json
{
"replication": true,
"autoDeploy": true,
"hotAlignment": true,
"resyncEvery": 15,
"clusters": {
"internal": {
"replication": false
},
"index": {
"replication": false
},
"*": {
"replication": true,
"readQuorum": 1,
"writeQuorum": 2,
"failureAvailableNodesLessQuorum": false,
"readYourWrites": true,
"partitioning": {
"strategy": "round-robin",
"default": 0,
"partitions": [
[ "<NEW_NODE>" ]
]
}
}
}
}
[2]
https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/1.7-SNAPSHOT/orientdb-community-1.7-20140409.215941-107-distribution.tar.gz
--
---
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.
