Hi guys, The RID is always the same across all the nodes. But the used sequence is per server. Playing with different clusters allows us to avoiding conflicts.
Unfortunately there is no way to force a clusterId on creation in distributed mode if that clusterId is assigned to another server. This is mandatory to avoid conflicts. @Mateusz, what's your use case? Lvc@ On 15 December 2014 at 10:39, Stéphane Schild <[email protected]> wrote: > > Thanks Lvc for your response ! > > To follow on Mateusz's question, is it really possible to have multiple > records with the same id across distributed nodes ? > Maybe is there some centralized sequence for cluster ids to avoid > different classes to use the same cluster ids ? > > -- > > --- > 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.
