It seems that it would be very useful for certain database cluster usage cases in distributed mode (ie. distributed chat or other event logs or pseudo-queues where order is more critical, and timestamps can't always be relied upon), if a particular cluster could be set to a "single leader" mode, so that basically you could still insert new objects from any master, but all writes will be forwards to a single active leader for that particular cluster. If for some reason that OrientDB instance disappears, a new leader will be elected for clusters where the lost node was designated as leader.
-- --- 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.
