ional
consistency between cache and DB.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9105.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Can I be sure that in case of commit failure Ignite will always invoke
CacheStore.load() for all invalidated objects?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9103.html
Sent from the Apache Ignite Users mailing
spend access to invalid objects
- flush Kafka to database (it can take several seconds)
- reload invalidated object from database
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9101.html
Sent from the Apache Ignite Use
hase-commit-for-distributed-in.html
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9099.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
nite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9096.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
To be honest I'm not sure I understand what you mean because these two topics
are completely unrelated to each other. Can you elaborate?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9090.html
Sent from the A
usage, invalidate cache(-s),
reload caches, switch-on cache usage ...
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9068.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
.nabble.com/Two-phase-commit-failure-recovery-tp9040p9066.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.