Re: Ignite Write Behind + .NET + External Cache Store

2024-01-15 Thread Pavel Tupitsyn
1. Write-behind mode invokes cache store in background, so there is no simple way to confirm if a particular write (cache put) has been persisted, no matter how many backups. 2. AFAIK, cache store is only invoked on the primary node for the given key On Tue, Jan 9, 2024 at 5:04 PM wrote: > Hi

Ignite Write Behind + .NET + External Cache Store

2024-01-09 Thread satyajit.mandal.barclays.com via user
Hi Pavel, Under Write Behind = true setting does Ignite will try to save data from backup node( partition) if lets say one node crashes while writing into external cache store? Document says if node crashes then some data can be lost from saving into external

Re: Ignite Write Behind performance

2016-06-09 Thread amitpa
We use it to conservative 2 now in our current setting -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5549.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Write Behind performance

2016-06-08 Thread bintisepaha
Thanks for that. we were setting flushsize to 0. how about flush thread count? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5541.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Write Behind performance

2016-06-06 Thread amitpa
I did test this...For us I think Write behind gets called fine. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5475.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Write Behind performance

2016-06-06 Thread bintisepaha
that? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5470.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Write Behind performance

2016-06-04 Thread amitpa
Thanks we are considering implementing JDBC batch inserts -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5418.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Write Behind performance

2016-06-03 Thread Alexey Goncharuk
gt; > What I mean is :- > > Shouldnt the write behind use a separete thread pool so that slow write > behind process does not impact the whole grid ? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performan

Re: Ignite Write Behind performance

2016-06-03 Thread amitpa
I understood this perfectly. What I mean is :- Shouldnt the write behind use a separete thread pool so that slow write behind process does not impact the whole grid ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5412

Re: Ignite Write Behind performance

2016-06-03 Thread Denis Magda
the cost of slow disk IO. > I understand that theres a limit, but shouldnt this thread pool be different > if technically possible, allowing ignite to continue processing in case of > slow write behind performance. > > > > -- > View this message in context: > http://ap

Re: Ignite Write Behind performance

2016-06-03 Thread amitpa
ignite to continue processing in case of slow write behind performance. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5400.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Write Behind performance

2016-06-02 Thread Denis Magda
write behind mode. > > What should be my system threadpool size assuming I have two caches which > participate in transactions and 2 nodes in 10G network. > > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nab

Ignite Write Behind performance

2016-06-02 Thread amitpa
://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite WRite Behind

2016-05-05 Thread amitpa
); cacheCfg.setSwapEnabled(false); cacheCfg.setWriteBehindFlushFrequency(5000); cacheCfg.setOffHeapMaxMemory(0); Do I need to add something to it? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-WRite-Behind-tp4741p4797.html Sent from the Apache Ignite

Re: Ignite WRite Behind

2016-05-05 Thread amitpa
be called for the 3 entries. My transaction level is Optimistic with Serializable. Does this affect something? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-WRite-Behind-tp4741p4796.html Sent from the Apache Ignite Users mailing list archive

Re: Ignite WRite Behind

2016-05-04 Thread Vladimir Ozerov
writeThrough set to true and writeBehindEnabled set to true. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-WRite-Behind-tp4741p4748.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Ignite WRite Behind

2016-05-03 Thread amitpa
Hi, I have 2 nodes setup and there are around 5 different caches involved, with 1 entry per cache per transaction. I have writeThrough set to true and writeBehindEnabled set to true. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-WRite-Behind