[
https://issues.apache.org/jira/browse/GEODE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888388#comment-16888388
]
ASF subversion and git services commented on GEODE-6972:
--------------------------------------------------------
Commit 7e62cddea8597ba14e26ff7c81ab66654af22175 in geode's branch
refs/heads/develop from Dave Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7e62cdd ]
GEODE-6972: User Guide - Clarify behavior of gemfire.disk.recoverValues (#3811)
* GEODE-6972: User Guide - Clarify behavior of gemfire.disk.recoverValues(Sync)
and gemfire.disk.recoverLruValues. Add reminders that LRU history is not
recoverable
> User Guide - Clarify behavior of gemfire.disk.recoverValues(Sync) and
> gemfire.disk.recoverLruValues
> ---------------------------------------------------------------------------------------------------
>
> Key: GEODE-6972
> URL: https://issues.apache.org/jira/browse/GEODE-6972
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Dave Barnes
> Assignee: Dave Barnes
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Properties gemfire.disk.recoverValues and gemfire.disk.recoverValuesSync are
> disabled by default. When enabled, they read all the values from disk, even
> though a bunch of them might not fit in memory. So the system waits until the
> application reads something before recovering data. For the use cases that
> have overflow just to prevent running out of memory, but really expect never
> to overflow, users can enable the gemfire.disk.recoverLruValues property.
> Clarify this in the User Guide. Likely location:
> [https://geode.apache.org/docs/guide/19/managing/troubleshooting/system_failure_and_recovery.html]
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
