You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Karen Smoler Miller (JIRA)" <ji...@apache.org> on 2017/05/25 23:32:04 UTC

[jira] [Resolved] (GEODE-2985) Doc task: making/using backups when there are indexes

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

Karen Smoler Miller resolved GEODE-2985.
----------------------------------------
    Resolution: Invalid

Ticket has incorrect info.  Will open a new ticket with correct info.

> Doc task: making/using backups when there are indexes
> -----------------------------------------------------
>
>                 Key: GEODE-2985
>                 URL: https://issues.apache.org/jira/browse/GEODE-2985
>             Project: Geode
>          Issue Type: Bug
>          Components: docs
>            Reporter: Karen Smoler Miller
>            Assignee: Karen Smoler Miller
>
> We should document that making a backup or using a backup to restore a system when that system also has/had indexes can be problematic.
> When taking a backup on a system that has an index, if there are region operations in progress, the asynchronous nature of propagating the results of the operations to an index means that the index content may be inconsistent with the region content.  If the backup were later used to restore a system, the inconsistency will be introduced back into the system.
> The fix for this is to make sure that the system is quiescent with respect to region operations when a backup is taken.
> In addition, the restoration procedure should rebuild indexes.
> This issue exists for both regular (OQL) indexes and for Lucene indexes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)