Hi Sparkle, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
sparkle_j wrote > Hi Val, > > If write behind failed due to bad data, framework is constantly trying to > attempt (insert or update) forever. Hope you can make this re-try > configurable. We had to implement some more code to limit the number of > re-tries to 3. Wish this is configurable. > > Thanks, > Sparkle. Do you have several caches with write-behind being enabled? If it's so and there is a primary, foreign or unique key constraint then a store can come to the loop while a constrained is satisfied (a write-behind store of cacheA will wait and retry his updates until a write-behind store of cacheB inserts its data that will satisfy a constraint). In any case please share the full stack trace of your issue. -- Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Writebehind-retry-logic-tp6189p6295.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
