You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by Raja <ye...@gmail.com> on 2017/08/03 16:34:35 UTC

Re: Data loss validation. TopologyValidator

Appreciate if anyone has thoughts on how to solve the above issue



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-loss-validation-TopologyValidator-tp15147p15958.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Data loss validation. TopologyValidator

Posted by ezhuravlev <e....@gmail.com>.

TopologyValidator blocks cache write operations on this topology and it can
be unblocked only after new topology changes. 

Looks like Ignite doesn't have what you want out of the box and you need to
impelement it yourself. For example, you can introduce flag
isClusterAccessible, which will have default value "true" and will be set to
"false" when you received EVT_CACHE_REBALANCE_PART_DATA_LOST event



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-loss-validation-TopologyValidator-tp15147p16026.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.