mirror of
https://github.com/OpenHFT/Chronicle-Map.git
synced 2021-09-13 01:26:12 +00:00
Replication updates with local identifier shouldn't use the same timestamp, because this allows two different updates which replace each other on different nodes, and don't converge. Extend default TimeProvider precision to nanoseconds, to exclude possibility of 'microsecond overflow' on frequent changes to the same entry
This commit is contained in:
@@ -184,7 +184,7 @@ public final class ChronicleMapBuilder<K, V> implements
|
||||
private boolean removeReturnsNull = false;
|
||||
|
||||
// replication
|
||||
private TimeProvider timeProvider = MicrosecondPrecisionSystemTimeProvider.instance();
|
||||
private TimeProvider timeProvider = NanosecondPrecisionSystemTimeProvider.instance();
|
||||
/**
|
||||
* Default timeout is 1 minute. Even loopback tests converge often in the course of seconds,
|
||||
* let alone WAN replication over many nodes might take tens of seconds.
|
||||
|
||||
Reference in New Issue
Block a user