Thanks. I understand relying on user to determine if data is upto date when Ignite is used as a cache. With native persistence, Ignite is the source of the data. If some partitions become unavailable, there's no way for data to become outdated. Feels like there should be a configuration setting to allow Ignite to auto-recover when all partitions are back online for a cache with native persistence.
On Thu, Oct 4, 2018 at 10:54 AM Maxim.Pudov <[email protected]> wrote: > I'm not an architect of this feature, but the explanation could be quite > simple: data stored in lost partitions could have become outdated while > nodes containing data were out of the cluster, so it's up to user to decide > whether the restored data is OK, or not. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
