Github user dihardman commented on a diff in the pull request:
https://github.com/apache/geode/pull/544#discussion_r119445495
--- Diff: geode-docs/tools_modules/lucene_integration.html.md.erb ---
@@ -294,8 +294,11 @@ will return `object_2`.
will return `object_3`.
- Backups should only be made for regions with Lucene indexes
when there are no puts, updates, or deletes in progress.
-Incremental backups will not be consistent for the region and
-its index upon restart if these operations were in progress,
-due to the delayed processing associated with the asynchronous event queue.
-If region data needs to be restored from a backup,
-follow the same procedure as given for changing an index.
+A backup might cause an inconsistency between region data and a Lucene
index,
+if that backup is used to restore a system.
+The Lucene index is persistent.
+If a backup is unlucky enough to be taken between
+a persisted write to a region (causing a disk operation)
+and the resulting persisted write to the Lucene index
+(causing a disk operation),
+then the backup represents inconsistent data in the region and Lucene
index.
--- End diff --
See comments added to backup_restore_disk_store.erb
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
