You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/26 19:32:04 UTC
[jira] [Commented] (GEODE-2994) Doc task: interactions of backups
with persistence
[ https://issues.apache.org/jira/browse/GEODE-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026725#comment-16026725 ]
ASF GitHub Bot commented on GEODE-2994:
---------------------------------------
GitHub user karensmolermiller opened a pull request:
https://github.com/apache/geode/pull/544
GEODE-2994 Take backups when region ops are quiescent
@upthewaterspout @joeymcallister @davebarnes97 @dihardman @ladyVader @boglesby
Please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/karensmolermiller/geode feature/GEODE-2994
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/544.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #544
----
commit 4affd0b7103b7b6630b38c63ba8c2e1b5f4bd1a0
Author: Karen Miller <km...@pivotal.io>
Date: 2017-05-26T17:29:29Z
GEODE-2994 Take backups when region ops are quiescent
----
> 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
>
> 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.3.15#6346)