Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-15432

Make stable topology recovery more robust

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      java.lang.AssertionError: expected:<100> but was:<89>
	at org.infinispan.globalstate.AbstractGlobalStateRestartTest.checkData(AbstractGlobalStateRestartTest.java:218)
	at org.infinispan.globalstate.ThreeNodeTopologyReinstallTest.executeTestRestart(ThreeNodeTopologyReinstallTest.java:153)
	at org.infinispan.globalstate.ThreeNodeTopologyReinstallTest.testReinstallTopologySafely(ThreeNodeTopologyReinstallTest.java:60)
	at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
... Removed 21 stack frames

      A possible cause is the store is cleared for one of the nodes after the topology is manually installed. With numOwners=2 and having 2 nodes left on the cluster, the caches should still have all the data available.

       

      We need to ensure:

      1. To clear the storage only once after the stable topology is installed;
      2. Checking if the stable topology was restored relies only on the future, so we are sure the restore process is finished.

       

              rh-ee-jbolina Jose Bolina
              rh-ee-jbolina Jose Bolina
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: