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

Posted to issues@geode.apache.org by "Fred Krone (JIRA)" <ji...@apache.org> on 2017/07/25 16:01:00 UTC

[jira] [Updated] (GEODE-3293) Rapid Recovery Improvements

     [ https://issues.apache.org/jira/browse/GEODE-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Krone updated GEODE-3293:
------------------------------
    Summary: Rapid Recovery Improvements  (was: Option to invalidate state data after a cluster crash)

> Rapid Recovery Improvements
> ---------------------------
>
>                 Key: GEODE-3293
>                 URL: https://issues.apache.org/jira/browse/GEODE-3293
>             Project: Geode
>          Issue Type: Wish
>          Components: persistence
>            Reporter: Fred Krone
>              Labels: rapid_recovery
>
> This story is an epic to wrap mitigating to stale cache data.
> When GemFire is used is a fast moving data scenario every second it is down its data becomes more stale vs a system of record like a backing DB.  When the cluster is recovered its data will essentially be an aging snapshot.  In scenarios where data accuracy is essential (always?) it would be nice to have an option to invalidate stale data before allowing reads.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)