Disabling anti-entropy messages to stabilize performance of intent store
Change-Id: Ic66c6d710e6bc4bc82496c38a5b9955e58f72e73
diff --git a/core/store/dist/src/main/java/org/onosproject/store/ecmap/EventuallyConsistentMapImpl.java b/core/store/dist/src/main/java/org/onosproject/store/ecmap/EventuallyConsistentMapImpl.java
index 3b2129f3..69dc4a4 100644
--- a/core/store/dist/src/main/java/org/onosproject/store/ecmap/EventuallyConsistentMapImpl.java
+++ b/core/store/dist/src/main/java/org/onosproject/store/ecmap/EventuallyConsistentMapImpl.java
@@ -46,7 +46,6 @@
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.ScheduledExecutorService;
-import java.util.concurrent.TimeUnit;
import java.util.stream.Collectors;
import static com.google.common.base.Preconditions.checkNotNull;
@@ -154,9 +153,10 @@
groupedThreads("onos/ecm", mapName + "-bg-%d")));
// start anti-entropy thread
- backgroundExecutor.scheduleAtFixedRate(new SendAdvertisementTask(),
- initialDelaySec, periodSec,
- TimeUnit.SECONDS);
+ //FIXME need to re-enable
+// backgroundExecutor.scheduleAtFixedRate(new SendAdvertisementTask(),
+// initialDelaySec, periodSec,
+// TimeUnit.SECONDS);
updateMessageSubject = new MessageSubject("ecm-" + mapName + "-update");
clusterCommunicator.addSubscriber(updateMessageSubject,