Yes we fill the cache manually after a cluster is started. We load data to Ignite for use it for ultra fast access and fast updates (millions of updates/minute) where traditional databases cannot handle.
But we cannot afford to lose data on the cluster. if we lose a portion of data, the rest of the cluster is useless because of data inconsistency We would like to configure our cluster in such a way that its resilient to node failures. We cannot afford to lose data on the cluster. Appreciate if you can recommend the kind of configuration that needs to be used for such kind of resilient behavior. Thanking you Raja -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Local-node-SEGMENTED-Data-Lost-on-a-Partitioned-Cache-with-backups-of-3-tp11683p11726.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
