updateChange() should always be called after replicationStateUpdate(), because updateChange() uses the new timestamp

This commit is contained in:
leventov
2015-12-20 18:33:47 +03:00
parent dd4fa03bfe
commit 60de795949
2 changed files with 3 additions and 3 deletions
@@ -74,8 +74,8 @@ public abstract class ReplicatedMapSegmentIteration<K, V, R> extends MapSegmentI
checkOnEachPublicOperation.checkOnEachPublicOperation();
try {
entry.innerDefaultReplaceValue(newValue);
ru.updateChange();
e.updatedReplicationStateOnPresentEntry();
ru.updateChange();
} finally {
s.innerWriteLock.unlock();
}
@@ -138,8 +138,8 @@ public abstract class ReplicatedMapSegmentIteration<K, V, R> extends MapSegmentI
e.innerDefaultReplaceValue(value);
s.incrementModCount();
e.writeEntryPresent();
ru.updateChange();
e.updatedReplicationStateOnPresentEntry();
ru.updateChange();
} finally {
s.innerWriteLock.unlock();
}
@@ -95,7 +95,7 @@ public abstract class ReplicatedMapQuery<K, V, R> extends MapQuery<K, V, R>
@Override
public void doReplaceValue(Data<V> newValue) {
super.doReplaceValue(newValue);
ru.updateChange();
e.updatedReplicationStateOnPresentEntry();
ru.updateChange();
}
}