Hi Val, Our use case :
1. Read records from file 2. Do computations on each record 3. Put them in the cache and persistence using write behind. 4. When all the records from file are processed, updated in Cache and also persisted to DB, we want to trigger some other process which will do next set of operations on these records from cache. 5. We want to trigger this next process and mark original file as processed, only when we are sure data is persisted, so that in case of Node failure we need not process that file again. On Thu, Apr 27, 2017 at 10:26 AM, steve.hostettler < steve.hostett...@gmail.com> wrote: > Hi Val, > > the use case is the following > > 1) Load data into the database from an external system > 2) Once ready load it into the grid > 3) Process something that does massive write behinds > 4) Take a snapshot of the results (or) Do a backup of the tables <<--- At > this point I need the eventual consistency to ...eventually be > > At step 4 I cannot afford to have some update still in progress. This is > even more important since because of write behind I cannot maintain > referential integrity (since the insert/update are done in a random order) > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Write-behind-and-eventual- > consistency-tp12242p12287.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
