You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/26 18:05:10 UTC

[jira] [Closed] (GEODE-6972) User Guide - Clarify behavior of gemfire.disk.recoverValues(Sync) and gemfire.disk.recoverLruValues

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

Dick Cavender closed GEODE-6972.
--------------------------------

> 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
>             Fix For: 1.10.0
>
>          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
(v8.3.4#803005)