Do you see the same behaviour with older versions of Ignite, or is this unique to 2.16?
On Tue, 9 Jul 2024 at 21:34, Raymond Liu <philosob...@gmail.com> wrote: > Hi all, > > We're encountering an issue where entry processors execute twice. > Executing twice is a problem for us because, for easier optimization, we > would like our entry processors *not* to be idempotent. > > Here is a sample self-contained junit test on Github which demonstrates > this issue: https://github.com/Philosobyte/ignite > -duplicate-processing-test/blob/main/src/test/java/com/philosobyte/igniteduplicateprocessingtest/DuplicateProcessingTest.java > > > (in case that link doesn't work, my github username is Philosobyte and the > project is called "ignite-duplicate-processing-test") > > When the test is run, it will log two executions instead of just one. > > To rule out the entry processor executing on both a primary and backup > partition, I set the number of backups to 0. I've also set atomicityMode to > ATOMIC. > > Does anyone have any ideas about why this might happen? > > Thank you, > Raymond >
