I'm hoping someone can explain the new clustering scheme in 2.0, as the 
documentation doesn't seem to reflect what I'm seeing while testing M3.

I have two distributed instances running on Node1 and Node2.

The database I'm testing against has minimumclusters set to 1.

If I use the console and connect to Node1 and execute CREATE CLASS TEST, 
this is the result:

If I look at the files under *Node1*:databases/<dbname>/, I see these get 
created:
test.cpm
test.pcl
test_node1.cpm
test_node1.pcl

But, if I look at the files under *Node2*:databases/<dbname>/, I only see 
these get created:
test.cpm
test.pcl

However, if I restart the console on Node1 and execute the 'clusters' 
command, only test shows up.

Now, if I restart the OrientDB server on Node1 and then reconnect to the 
console and issue 'clusters', then both test and test_node1 show up as 
clusters.

If I restart OrientDB server on Node2, then things really change.

If I look at the files under Node1:databases/<dbname>/, I see these get 
created:
test.cpm
test.pcl
test_node1.cpm
test_node1.pcl
test_node2.cpm
test_node2.pcl

If I look at the files under Node2:databases/<dbname>/, I see these get 
created:
test.cpm
test.pcl
test_node1.cpm
test_node1.pcl
test_node2.cpm
test_node2.pcl

It doesn't always happen like this.  Sometimes I can be connected to the 
console on Node1, create a class, and it will create a local cluster with 
the class's name, and on the remote node it will create a cluster called 
classname_nodename.

First, why are clusters being created such as classname (expected 
behavior), classname_nodename1 (unexpected), and classname_nodename2 
(unexpected)?

Second, why do the clusters with the nodename appended for all running 
servers not show up until both OrientDB services are restarted?

Thanks for any insight!

-Colin

-- 

--- 
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.

Reply via email to