You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by al...@apache.org on 2021/03/23 11:06:44 UTC
[geode] branch develop updated: GEODE-8985: Fix doc references to
'startup-recovery-delay' (#6138)
This is an automated email from the ASF dual-hosted git repository.
alberto pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new 81b8f46 GEODE-8985: Fix doc references to 'startup-recovery-delay' (#6138)
81b8f46 is described below
commit 81b8f460d63ed98d67478e7d4cc2616d9c8ee433
Author: Alberto Bustamante Reyes <al...@users.noreply.github.com>
AuthorDate: Tue Mar 23 12:05:31 2021 +0100
GEODE-8985: Fix doc references to 'startup-recovery-delay' (#6138)
---
.../partitioned_regions/checking_region_redundancy.html.md.erb | 4 ++--
.../partitioned_regions/restoring_region_redundancy.html.md.erb | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb b/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
index 3779c38..4087e8a 100644
--- a/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
+++ b/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
@@ -42,8 +42,8 @@ Initiate an operation to report the current redundancy status of regions using o
System.out.println("Status for region " + regionName + ": " + currentStatus.getRegionResult(regionName).getMessage();
```
-If you have `start-recovery-delay=-1` configured for your partitioned region, you will need to trigger a restore redundancy operation on your region after you restart any members in your cluster in order to recover redundancy. See [Restoring Redundancy in Partitioned Regions](restoring_region_redundancy.html).
+If you have `startup-recovery-delay=-1` configured for your partitioned region, you will need to trigger a restore redundancy operation on your region after you restart any members in your cluster in order to recover redundancy. See [Restoring Redundancy in Partitioned Regions](restoring_region_redundancy.html).
-If you have `start-recovery-delay` set to a low number, you may need to wait extra time until the region has recovered redundancy.
+If you have `startup-recovery-delay` set to a low number, you may need to wait extra time until the region has recovered redundancy.
diff --git a/geode-docs/developing/partitioned_regions/restoring_region_redundancy.html.md.erb b/geode-docs/developing/partitioned_regions/restoring_region_redundancy.html.md.erb
index 5ad9f86..8f801d3 100644
--- a/geode-docs/developing/partitioned_regions/restoring_region_redundancy.html.md.erb
+++ b/geode-docs/developing/partitioned_regions/restoring_region_redundancy.html.md.erb
@@ -52,8 +52,8 @@ Initiate a restore redundancy operation using one of the following:
System.out.println("Results for region " + regionName + ": " + results.getRegionResult(regionName).getMessage();
```
-If you have `start-recovery-delay=-1` configured for your partitioned region, you will need to perform a restore redundancy operation on your region after you restart any members in your cluster in order to recover any lost redundancy.
+If you have `startup-recovery-delay=-1` configured for your partitioned region, you will need to perform a restore redundancy operation on your region after you restart any members in your cluster in order to recover any lost redundancy.
-If you have `start-recovery-delay` set to a low number, you may need to wait extra time until the region has recovered redundancy.
+If you have `startup-recovery-delay` set to a low number, you may need to wait extra time until the region has recovered redundancy.