I think it's related to a reported bugs few days back https://github.com/orientechnologies/orientdb/issues/3311
On Tuesday, 6 January 2015 17:21:12 UTC+8, Leng Sheng Hong wrote: > > Is auto sharding working in 2.0 RC1? > > I have 2 servers nodes with orientdb distributed mode running. Both > database are synced. I have tried to enable autosharding following the > manual at > http://www.orientechnologies.com/docs/last/orientdb.wiki/Distributed-Sharding.html > > and create my claases. > > alter database minimumclusters 4 > > > The DB clusterSelection was roundrobin. However when i insert records > it's always using the default cluster, no other clusters are used to store > the new records. > So i tried to alter the cluster selection for the class: ALTER CLASS > MyProfile CLUSTERSELECTION roundrobin > > Tried to create new record, it's still using the default #18 cluster. > After changing to another clusterselection > ALTER CLASS MyProfile CLUSTERSELECTION balanced > > It's still the same, however now when i insert new record from server 2, > it will complai: > com.orientechnologies.common.exception.OException: Cannot find best > cluster for class 'MyProfile'. ClusterStrategy=local > [ONetworkProtocolHttpDb] > > But it's still fine on server 1 but still only the default cluster is > used. (which is the 1st DB that is deploy). What else is needed to be > configured to New records to fully utilize the clusters automatically? > > Name SuperClass AliasAbstractClusters Default ClusterCluster Selection > RecordsActionsMyProfile[18,19,20,21]18 > > -- --- 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.
