Ok i found !
18:36:07 noringBase.info INFO Topology snapshot [ver=2,
locNode=2bf85583, servers=2, clients=0, state=ACTIVE, CPUs=8, offheap=6.3GB,
heap=3.5GB]
18:36:07 noringBase.info INFO ^-- Baseline [id=0, size=1,
online=1, offline=0]
you call baseline command after first node was started, thus you have 2 alive
nodes with only one in baseline.
clear your persistent directories, and rewrite code like :
startNode(...a..)
ignite = startNode(..b...)
ignite.cluster().state(ClusterState.ACTIVE);
>
>>
>>>Hi Zhenya,
>>>To be on the safe side, I increased the sleep to 5 sec. I also removed the
>>>setBackups(2) – no difference – the test is still failing!
>>>
>>>Newest log file with corresponding source attached.
>>>
>>>I added more specific logs:
>>>
>>>18:36:07 lusterTest.testMem2 INFO >>>>>> value has been written to
>>>'a': aval
>>>18:36:12 lusterTest.testMem2 INFO >>>>>> value retrieved from 'b':
>>>null
>>>
>>>---
>>>Mit freundlichen Grüßen
>>>
>>>Stephan Hesse
>>>Geschäftsführer
>>>
>>>DICOS GmbH Kommunikationssysteme
>>>Alsfelder Straße 11, 64289 Darmstadt
>>>
>>>Telefon: +49 6151 82787 27 , Mobil: +49 1761 82787 27
>>>
>>>www.dicos.de
>>>
>>>DICOS GmbH Kommunikationssysteme, Darmstadt, Amtsgericht Darmstadt HRB 7024,
>>>Geschäftsführer: Dr. Winfried Geyer, Stephan Hesse, Waldemar Wiesner
>>>
>>>
>>>
>>>From: Zhenya Stanilovsky < arzamas...@mail.ru >
>>>Sent: Monday, March 1, 2021 7:15 AM
>>>To: user@ignite.apache.org
>>>Subject: Re[4]: Mixing persistent and in memory cache
>>>
>>>
>>>hi Stephan, due to logs rebalance still in progress (probably slow
>>>network ?) will test pass if you increase sleep interval ? 2 sec fro example
>>>?
>>>Additionally no need to set .setBackups(2) in CacheMode.REPLICATED cache,
>>>plz check documentation.
>>>
>>>
>>>>Hi Zhenya,
>>>>
>>>>your 2nd point: yes, the cache itself has been propagated.
>>>>
>>>>Please be aware that I have successfully used the same test with only the
>>>>in-memory region as well as with only the persistent region. Only when I
>>>>combine both, the synchronization stops working for the in memory region.
>>>>
>>>>
>>>>Please find attached the log file (both Ignite nodes run in the same
>>>>process and contribute to this log file) as well as the current Junit test.
>>>>
>>>>In the log file you will find:
>>>>
>>>>The node startup:
>>>>>>>> starting node A
>>>>>>>> starting node B
>>>>
>>>>The test case startup:
>>>>#### testMem2
>>>>
>>>>The test stops with:
>>>>java.lang.AssertionError: expected:<aval> but was:<null>
>>>> …
>>>> at
>>>>de.dicos.cpcfe.ignite.IgniteClusterTest.testMem2(IgniteClusterTest.java:175)
>>>>
>>>>---
>>>>Mit freundlichen Grüßen
>>>>
>>>>Stephan Hesse
>>>>Geschäftsführer
>>>>
>>>>DICOS GmbH Kommunikationssysteme
>>>>Alsfelder Straße 11, 64289 Darmstadt
>>>>
>>>>Telefon: +49 6151 82787 27 , Mobil: +49 1761 82787 27
>>>>
>>>>www.dicos.de
>>>>
>>>>DICOS GmbH Kommunikationssysteme, Darmstadt, Amtsgericht Darmstadt HRB 7024,
>>>>Geschäftsführer: Dr. Winfried Geyer, Stephan Hesse, Waldemar Wiesner
>>>>
>>>>
>>>>
>>>>From: Zhenya Stanilovsky < arzamas...@mail.ru >
>>>>Sent: Friday, February 26, 2021 6:57 AM
>>>>To: user@ignite.apache.org
>>>>Subject: Re[2]: Mixing persistent and in memory cache
>>>>
>>>>
>>>>hi Stephan, something wrong with configuration probably … it`s not expected
>>>>issue.
>>>>* plz attach somehow or send me ignite.log from all server nodes ?
>>>>* If you change second call :
>>>>IgniteCache<String, String> kva = getInMemoryKeyValue(igA);
>>>>
>>>> IgniteCache<String, String> kvb = getInMemoryKeyValue(igB); ← here
>>>>for something like : IgniteCache<String, String> kvb =
>>>>getInMemoryKeyValue2(igB);
>>>>
>>>>private IgniteCache<String, String> getInMemoryKeyValue2(Ignite ignite)
>>>> {
>>>> return ignite.cache(new CacheConfiguration<String, String>() <---
>>>>
>>>>just to check that cache has been already created.
>>>>
>>>>Does ignite.cache will see the previously created cache ?
>>>>
>>>>thanks !
>>>>
>>>>
>>>>>Hi Zhenya, thanks for this suggestion.
>>>>>
>>>>>However, neither setting CacheWriteSynchronizationMode to Full Sync nor
>>>>>setting it to FULL_ASYNC changes anything: memory cahce changes do not get
>>>>>propagated:
>>>>>
>>>>>private IgniteCache<String, String> getInMemoryKeyValue(Ignite ignite)
>>>>>{
>>>>>return ignite.getOrCreateCache(new CacheConfiguration<String, String>()
>>>>>.setName("memkv")
>>>>>.setCacheMode(CacheMode.REPLICATED)
>>>>>.setDataRegionName(NodeController.IN_MEMORY_REGION)
>>>>>.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
>>>>>.setBackups(2));
>>>>>}
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
