As I asked in another post: is there a way to make all the clusters of a same class share the cluster position? As I mentioned I (and I would suspect others?) rely on Orient's id generation and having suddenly X records with the same id because it's in a different class isn't an option...
Mateusz On Sunday, December 14, 2014 5:29:51 AM UTC+9, Lvc@ wrote: > > Hi Stephane, > In distributed mode the RID is assigned with cluster locality for each > class. If you have class Customer and 3 nodes (node1, node2, node3), you'll > have these clusters: > > 1. customer (this is the default one, assigned to node1), id=#15 > 2. customer_node2, id=#16 > 3. customer_node3, id=#17 > > So if you create a new Customer on node1, it will get the ClusterID of > "customer" cluster: 15. The same operation on node2, will generate a RID > with clusterId=16 and 17 on node3. > > In this way RID never collide and each node can be a real multi-master > even on insertion without conflicts. > > Lvc@ > > > On 12 December 2014 at 15:22, Stéphane Schild <[email protected] > <javascript:>> wrote: >> >> Hi, >> >> I was wondering how were generated the RecordIDs in distributed mode. Is >> there something like a centralized sequence somewhere ? >> >> I know that the RecordID consists of <cluster_id>:<position>, but I don't >> understand how is managed the use case when multiple nodes create objects >> in the same cluster at the same time. >> >> Thanks ! >> >> -- >> >> --- >> 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] <javascript:>. >> 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.
