/Scenario : If there are multiple node failures occurred at the same time and ignite loses primary and as well as backup copies of partitions and how to know if this happened and data is lost?
Once you detect the data loss, how to restrict/reject clients and because the cache is partial and not complete. Once the system loads lost partitions then ignite should allow the users to use the cache / I was trying to come up with a solution for the above scenario and tried to use "TopologyValidator" & "EVT_CACHE_REBALANCE_PART_DATA_LOST" as suggested above. But I ran into chicken and egg problem. I was able to capture data loss event and reload data on a data loss event. I implemented "TopologyValidator" to check the row count and block clients from read/writing the cache, but with this approach the cache loader is also NOT able to read/write the cache. How to allow cache loader to write to cache, but blocks other users from using the cache. Wonder if anyone has run into this situation and how you solved. Or is there any cleaner way to solve this issue. Appreciate your inputs. Raja -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-loss-validation-TopologyValidator-tp15147p15833.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
