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.
