You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2017/09/21 22:53:22 UTC
[geode] 03/03: Incorporate reviewer corrections (kmiller)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
commit 79c2d26528ef32045eb05e375f2ed9c911a2913d
Author: Dave Barnes <db...@pivotal.io>
AuthorDate: Thu Sep 21 15:50:29 2017 -0700
Incorporate reviewer corrections (kmiller)
---
.../cache_snapshots/exporting_a_snapshot.html.md.erb | 5 +++--
.../cache_snapshots/importing_a_snapshot.html.md.erb | 2 +-
.../tools_modules/gfsh/command-pages/export.html.md.erb | 12 ++++++------
.../tools_modules/gfsh/command-pages/import.html.md.erb | 7 ++++---
4 files changed, 14 insertions(+), 12 deletions(-)
diff --git a/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb b/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
index 85d73af..38b9bc0 100644
--- a/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
+++ b/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
@@ -63,7 +63,7 @@ Open a gfsh prompt. After connecting to a <%=vars.product_name%> distributed sys
gfsh>export data --region=Region --file=FileName.gfd --member=MemberName
```
-where *Region* corresponds to the name of the region that you want to export, *FileName* (must end in .gfd) corresponds to the name of the export file and *MemberName* corresponds to a member where the region to export is hosted. For example:
+where *Region* corresponds to the name of the region that you want to export, *FileName* (must end in .gfd) corresponds to the name of the export file and *MemberName* corresponds to a member that hosts the region. For example:
``` pre
gfsh>export data --region=region1 --file=region1_2012_10_10.gfd --member=server1
@@ -82,7 +82,8 @@ Note that the `parallel` option takes a directory rather than a file; see [expor
File mySnapshotDir = ...
Region<String, MyObject> region = ...
-SnapshotOptions<Integer, MyObject> options = region.getSnapshotServive.createOptions().setParallelMode(true);
+SnapshotOptions<Integer, MyObject> options =
+ region.getSnapshotServive.createOptions().setParallelMode(true);
region.getSnapshotService().save(mySnapshotDir, SnapshotFormat.GEMFIRE, options);
```
diff --git a/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb b/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb
index 6e9f558..bc8d644 100644
--- a/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb
+++ b/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb
@@ -68,7 +68,7 @@ Open a gfsh prompt. After connecting to a <%=vars.product_name%> distributed sys
gfsh>import data --region=Region --file=FileName.gfd --member=MemberName
```
-where *Region* corresponds to the name of the region that you want to import data into; *FileName* (must end in .gfd) corresponds to the name of the file to be imported; and *MemberName* corresponds to the member where the region to be imported is hosted. For example:
+where *Region* corresponds to the name of the region that you want to import data into; *FileName* (must end in .gfd) corresponds to the name of the file to be imported; and *MemberName* corresponds to a member that hosts the region. For example:
``` pre
gfsh>import data --region=region1 --file=region1_2012_10_10.gfd --member=server2
diff --git a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
index 8fa0941..203fdd8 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
@@ -71,14 +71,14 @@ export cluster-configuration --zip-file-name=value [--dir=value]
**Example Commands:**
``` pre
-gfsh>export cluster-configuration --zip-file-name=/home/username/gemfire80/myClusterConfig.zip
+gfsh>export cluster-configuration --zip-file-name=/home/username/gemfire/myClusterConfig.zip
```
**Sample Output:**
``` pre
gfsh>export cluster-configuration --zip-file-name=mySharedConfig.zip
-Downloading cluster configuration : /home/username/gemfire80/myClusterConfig.zip
+Downloading cluster configuration : /home/username/gemfire/myClusterConfig.zip
```
## <a id="topic_C7C69306F93743459E65D46537F4A1EE" class="no-quick-link"></a>export config
@@ -115,8 +115,8 @@ export config --members=member1
``` pre
gfsh>export config --members=member1
-Downloading Cache XML file: c:\PivotalGemFire70\Latest\.\member1-cache.xml
-Downloading properties file: c:\PivotalGemFire70\Latest\.\member1-gf.properties
+Downloading Cache XML file: c:\PivotalGemFire\Latest\.\member1-cache.xml
+Downloading properties file: c:\PivotalGemFire\Latest\.\member1-gf.properties
```
## <a id="topic_263B70069BFC4A7185F86B3272011734" class="no-quick-link"></a>export data
@@ -167,7 +167,7 @@ export data --region=region2 --file=region2_20121001.gfd --member=server2
``` pre
gfsh>export data --region=region2 --file=region2_20121001.gfd --member=server1
-Data succesfully exported from region : region2 to file : C:\PivotalGemFire70\
+Data succesfully exported from region : region2 to file : C:\PivotalGemFire\
Latest\server1\region2_20121001.gfd on host : 192.0.2.0
```
@@ -280,6 +280,6 @@ export stack-traces --file=stack.txt
``` pre
gfsh>export stack-traces --file=stack.txt
-stack-trace(s) exported to file: C:\PivotalGemFire70\Latest\locator1\stack.txt
+stack-trace(s) exported to file: C:\PivotalGemFire\Latest\locator1\stack.txt
On host : GemFireStymon
```
diff --git a/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb
index eca2336..b22ae4b 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb
@@ -38,7 +38,7 @@ upgrading from an older version of <%=vars.product_name%> to a new one.
- In a given cluster, only one locator needs to perform the import.
That locator shares the imported configuration with all other connected locators in the distributed system.
-- Locators share the imported configuration with data members (servers) when they start, or if they have been recently started and no other
+- Locators share the imported configuration with data members (servers) when the servers start, or if the servers have been recently started and no other
configuration changes have been made (such as new region definitions, for example).
- Data members that were already running before the import may need to be restarted to obtain the new cluster configuration.
@@ -97,7 +97,8 @@ See [export data](export.html#topic_263B70069BFC4A7185F86B3272011734) for an exp
If the data was exported from a partitioned region in parallel format, use the `--parallel` option to import the data:
``` pre
-import data --parallel --region=value --member=value --dir=value [--invoke-callbacks=value]
+import data --parallel --region=value --member=value --dir=value
+ [--invoke-callbacks=value]
```
In this scenario, partitioned region data is imported simultaneously on all hosting nodes from directories local to those respective nodes.
@@ -113,7 +114,7 @@ In this scenario, partitioned region data is imported simultaneously on all host
|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
| <span class="keyword parmname">\\-\\-region</span> | *Required.* Region into which data will be imported. | |
| <span class="keyword parmname">‑‑member</span> | *Required.* Name/ID of a member that hosts the region. In a serial import, all data is imported from the specified file on the host where the member is running. In a parallel import, data from a partitioned region partially hosted on this member is imported for each partition from files on the nodes that host those partitions. | |
-| <span class="keyword parmname">\\-\\-file </span> | File from which the imported data will be read. The file must have an extension of ".gfd" and must be on the file system of the member (or accessible to that member via NFS) that is being targeted for the import. Cannot be specified at the same time as \\-\\-dir, cannot be used with ‑‑parallel. | |
+| <span class="keyword parmname">\\-\\-file </span> | File from which the imported data will be read. The file must have an extension of `.gfd` and must be on the file system of the member (or accessible to that member via NFS) that is being targeted for the import. Cannot be specified at the same time as \\-\\-dir, cannot be used with ‑‑parallel. | |
| <span class="keyword parmname">\\-\\-dir</span> | Directory from which the data is to be imported. Required if \\-\\-parallel is true. Cannot be specified at the same time as \\-\\-file. If a given node has no data file in the specified directory, the import operation is silently skipped for that node. | |
| <span class="keyword parmname">‑‑invoke‑callbacks</span> | Boolean value that, when true, invokes callbacks during the data import. | false |
--
To stop receiving notification emails like this one, please contact
"commits@geode.apache.org" <co...@geode.apache.org>.