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
The following commit(s) were added to refs/heads/develop by this push:
new da45b65 User Guide: Data Storage corrections
new 7c344c0 Merge branch 'feature/disk-store-doc' into develop
da45b65 is described below
commit da45b655888594c8744119dced130517cbc8b7f6
Author: Dave Barnes <[email protected]>
AuthorDate: Mon Oct 23 13:56:46 2017 -0700
User Guide: Data Storage corrections
---
.../disk_storage/file_names_and_extensions.html.md.erb | 15 ++++-----------
.../disk_storage/how_disk_stores_work.html.md.erb | 17 +++++++++--------
2 files changed, 13 insertions(+), 19 deletions(-)
diff --git
a/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
index 727f23b..18b1239 100644
--- a/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
+++ b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
@@ -26,7 +26,7 @@ The next tables describe file names and extensions; they are
followed by example
## <a id="file_names_and_extensions__section_C99ABFDB1AEA4FE4B38F5D4F1D612F71"
class="no-quick-link"></a>File Names
-File names have three parts:
+File names have three parts: usage identifier, disk store name, and oplog
sequence number.
**First Part of File Name: Usage Identifier**
@@ -62,35 +62,28 @@ File names have three parts:
Example files for disk stores persistDS1 and overflowDS1:
``` pre
-bash-2.05$ ls -tlra persistData1/
+bash-2.05$ ls -tlr persistData1/
total 8
-rw-rw-r-- 1 person users 188 Mar 4 06:17 BACKUPpersistDS1.if
-drwxrwxr-x 2 person users 512 Mar 4 06:17 .
-rw-rw-r-- 1 person users 0 Mar 4 06:18 BACKUPpersistDS1_1.drf
-rw-rw-r-- 1 person users 38 Mar 4 06:18 BACKUPpersistDS1_1.crf
-drwxrwxr-x 8 person users 512 Mar 4 06:20 ..
-bash-2.05$
-bash-2.05$ ls -ltra overflowData1/
+bash-2.05$ ls -tlr overflowData1/
total 1028
-drwxrwxr-x 8 person users 512 Mar 4 06:20 ..
-rw-rw-r-- 1 person users 0 Mar 4 06:21 DRLK_IFoverflowDS1.lk
-rw-rw-r-- 1 person users 0 Mar 4 06:21 BACKUPoverflowDS1.if
-rw-rw-r-- 1 person users 1073741824 Mar 4 06:21 OVERFLOWoverflowDS1_1.crf
-drwxrwxr-x 2 person users 512 Mar 4 06:21 .
```
Example default disk store files for a persistent region:
``` pre
-bash-2.05$ ls -tlra
+bash-2.05$ ls -tlr
total 106
-drwxrwxr-x 8 person users 1024 Mar 8 14:51 ..
-rw-rw-r-- 1 person users 1010 Mar 8 15:01 defTest.xml
drwxrwxr-x 2 person users 512 Mar 8 15:01 backupDirectory
-rw-rw-r-- 1 person users 0 Mar 8 15:01 DRLK_IFDEFAULT.lk
-rw-rw-r-- 1 person users 107374183 Mar 8 15:01 BACKUPDEFAULT_1.drf
-rw-rw-r-- 1 person users 966367641 Mar 8 15:01 BACKUPDEFAULT_1.crf
-rw-rw-r-- 1 person users 172 Mar 8 15:01 BACKUPDEFAULT.if
-drwxrwxr-x 3 person users 512 Mar 8 15:01 .
```
diff --git a/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb
b/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb
index 5d8a89e..85f2a08 100644
--- a/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb
+++ b/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb
@@ -37,13 +37,14 @@ This figure shows a member with disk stores D through R
defined. The member has
## <a id="how_disk_stores_work__section_433EEEA1560D40DD9842200181EB1D0A"
class="no-quick-link"></a>What <%=vars.product_name%> Writes to the Disk Store
-This list describes the items that <%=vars.product_name%> comprise the disk
store:
+<%=vars.product_name%> writes the following to the disk store:
-- The members that host the store, and information on their status, such as
which members are online and which members are offline and time stamps.
-- A disk store identifier.
-- Which regions are in the disk store, specified by region name.
-- Colocated regions that the regions in the disk store are dependent upon.
-- A set of files that specify all keys for the regions, as well as all
operations on the regions. Given both keys and operations, a region can be
recreated when a member is restarted.
+- Persisted and overflowed data as specified when the disk store was created
and configured
+- The members that host the store and information on their status, such as
which members are online and which members are offline and time stamps
+- A disk store identifier
+- Which regions are in the disk store, specified by region name and
including selected attributes
+- Names of colocated regions on which the regions in the disk store depend
+- A record of all operations on the regions
<%=vars.product_name%> does not write indexes to disk.
@@ -52,9 +53,9 @@ This list describes the items that <%=vars.product_name%>
comprise the disk stor
The files for a disk store are used by <%=vars.product_name%> as a group.
Treat them as a single entity. If you copy them, copy them all together. Do not
change the file names.
Disk store access and management differs according to whether the member is
online or offline.
-
While a member is running, its disk stores are online. When the member exits
and is not running, its disk stores are offline.
- Online, a disk store is owned and managed by its member process. To run
operations on an online disk store, use API calls in the member process, or use
the `gfsh` command-line interface.
-- Offline, the disk store is just a collection of files in the host file
system. The files are accessible based on file system permissions. You can copy
the files for backup or to move the member’s disk store location. You can also
run some maintenance operations, such as file compaction and validation, by
using the `gfsh` command-line interface. When offline, the disk store's
information is unavailable to the distributed system. For partitioned regions,
region data is split between mu [...]
+- Offline, the disk store is just a collection of files in the host file
system. The files are accessible based on file system permissions. You can copy
the files for backup or to move the member’s disk store location. You can also
run some maintenance operations, such as file compaction and validation, by
using the `gfsh` command-line interface. When offline, the disk store's
information is unavailable to the distributed system.
+For partitioned regions, region data is split between multiple members, and
therefore the start up of a member is dependent onall members, and must wait
for all members to be online. An attempt to access an entry that is stored on
disk by an offline member results in a `PartitionOfflineException`.
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
