Hi Colin, Starting from 2.0-M3 each server node creates own cluster on join, so it's normal.
Lvc@ On 2 December 2014 at 22:39, Colin <[email protected]> wrote: > I noticed the same issue yesterday and posted a detailed question about it > this morning as well (OrientDB 2.0 Clusters). > > Hopefully someone will explain the intended behavior and why for the > clusters. It's not in any of the documentation. > > Regards, > > -Colin > > > On Tuesday, December 2, 2014 6:47:49 AM UTC-6, Sajal Gupta wrote: >> >> OrientDB Version: 2.0M3 >> Java 1.7 >> Windows 7 >> Default distributed config. - No change >> >> Steps followed :- >> Configured two nodes (node1 and node2) >> Started the standalone server on node1. >> Created a test database of type graph from the studio Web - The database >> is created fine. >> Shutdown the standalone server. >> Started dserver on node1 >> Started dserver on node2 -> The database is getting replicated fine. But >> now I see two clusters for every schema objects on both nodes >> For e.g. for V :- the following files are getting created on both >> nodes, Ditto for other classes. >> v.cpm >> v.pcl >> v_node2.cpm >> v_node2.pcl >> >> When I change the order of starting up the server (node2 first and then >> node1) :- one more cluster is getting created with _node1 appended. >> >> Let me know if this is a issue or am i doing something wrong.. >> >> Thanks >> Sajal >> >> > -- > > --- > 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. > -- --- 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.
