geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (GEODE-2994) Doc task: interactions of backups with persistence
Date Sat, 17 Jun 2017 18:04:34 GMT

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

Anthony Baker closed GEODE-2994.
--------------------------------

> Doc task: interactions of backups with persistence
> --------------------------------------------------
>
>                 Key: GEODE-2994
>                 URL: https://issues.apache.org/jira/browse/GEODE-2994
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs
>            Reporter: Karen Smoler Miller
>            Assignee: Karen Smoler Miller
>             Fix For: 1.2.0
>
>
> Document that an inconsistent state can occur by using a backup to restore system state,
if the backup is made at the wrong time.
> There are 2 examples where persistence and taking a backup might cause an inconsistency
with region data, if that backup is used to restore a system.
> # *A Lucene index.* The Lucene index is persistent. If a backup is unlucky enough to
be taken between a persisted write to a region (disk op) and a persisted write to the Lucene
index (disk op), then the backup represents inconsistent data in the region and Lucene index.
> # *An AEQ.* The AEQ is persistent. If a backup is unlucky enough to be taken between
a persisted write to a region (disk op) and a persisted write to the AEQ (disk op), then the
backup represents inconsistent data in the region and the AEQ.
> The solution is to make sure that backups are taken when the system is quiescent WRT
region operations.



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

Mime
View raw message