geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dbar...@apache.org
Subject geode git commit: GEODE-1672: When amount of overflowed persisted data exceeds heap size startup may run out of memory, corrections.
Date Mon, 05 Jun 2017 23:18:26 GMT
Repository: geode
Updated Branches:
  refs/heads/develop 40d36ba78 -> 1e11c5cc9


GEODE-1672: When amount of overflowed persisted data exceeds heap size startup may run out
of memory, corrections.


Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/1e11c5cc
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/1e11c5cc
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/1e11c5cc

Branch: refs/heads/develop
Commit: 1e11c5cc96c22123988e8d3480c0ebb2f2c2df6a
Parents: 40d36ba
Author: Dave Barnes <dbarnes@pivotal.io>
Authored: Mon Jun 5 16:18:24 2017 -0700
Committer: Dave Barnes <dbarnes@pivotal.io>
Committed: Mon Jun 5 16:18:24 2017 -0700

----------------------------------------------------------------------
 .../troubleshooting/system_failure_and_recovery.html.md.erb      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/geode/blob/1e11c5cc/geode-docs/managing/troubleshooting/system_failure_and_recovery.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/managing/troubleshooting/system_failure_and_recovery.html.md.erb b/geode-docs/managing/troubleshooting/system_failure_and_recovery.html.md.erb
index 740cc04..f4f921c 100644
--- a/geode-docs/managing/troubleshooting/system_failure_and_recovery.html.md.erb
+++ b/geode-docs/managing/troubleshooting/system_failure_and_recovery.html.md.erb
@@ -318,7 +318,7 @@ differently than non-LRU values.
 ## Default Recovery Behavior for Persistent Regions
 
 The default behavior is for the system to recover all keys, then asynchronously recover all
data
-values that were resident, leaving LRU values unrecovered. This default strategy is best
for
+values, leaving LRU values unrecovered. This default strategy is best for
 most applications, because it strikes a balance between recovery speed and cache completeness.
 
 ### Configuring Recovery of Persistent Regions
@@ -352,7 +352,7 @@ Three Java system parameters allow the developer to control the recovery
behavio
   no values are recovered.
 
   *How used:* When `false`, allows the system to become available sooner, but some time must
elapse
-  before the entire cache is refreshed. Some key retrievals will require disk access, and
some will not.
+  before all values have been read from disk into cache memory. Some key retrievals will
require disk access, and some will not.
   When `true`, prolongs restart time, but ensures that when available for use, the cache
is fully
   populated and data retrieval times will be optimal.
 


Mime
View raw message