Default removedEntryCleanupTimeout() 1 second -> 1 minute

This commit is contained in:
leventov
2015-10-03 05:10:54 +03:00
parent 7460074ac5
commit 9d3ff93021
2 changed files with 8 additions and 2 deletions
@@ -411,7 +411,7 @@ public interface ChronicleHashBuilder<K, H extends ChronicleHash<K, ?, ?, ?>,
* entry completely from the data structure. This timeout should depend on your distributed
* system topology, and typical replication latencies, that should be determined experimentally.
*
* <p>Default timeout is 1 second.
* <p>Default timeout is 1 minute.
*
* @param removedEntryCleanupTimeout timeout, after which stale removed entries could be erased
* from Chronicle Hash data structure completely
@@ -181,9 +181,15 @@ public final class ChronicleMapBuilder<K, V> implements
// replication
private TimeProvider timeProvider = MicrosecondPrecisionSystemTimeProvider.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.
*
* TODO review
*/
long cleanupTimeout = 1;
TimeUnit cleanupTimeoutUnit = TimeUnit.MINUTES;
private boolean cleanupRemovedEntries = true;
TimeUnit cleanupTimeoutUnit = TimeUnit.SECONDS;
private BytesMarshallerFactory bytesMarshallerFactory;
private ObjectSerializer objectSerializer;