Alexey, could you please help me understand, how do the DS backups affect a semaphore? Shouldn't the semaphore be replicated to all nodes?
I've re-tested the code with 2 backups configured, and three nodes started but to no avail. For three nodes it's even easier to reproduce: just start three nodes, and kill the one with the "acquired" message on the console. The "Failed to find ..." message will appear on the remaining nodes. Regards, Mario alexey.goncharuk wrote > As for the "Failed to find semaphore with the given name" message, my > first > guess is that DataStructures were configured with 1 backups which led to > the data loss when two nodes were stopped. Mario, can you please re-test > your semaphore scenario with 2 backups configured for data structures? > From my side, I can also take a look at the semaphore issue when I'm done > with IGNITE-2610. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-tp3031p3079.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
