Skip to content

Commit 9764005

Browse files
Merge pull request #542 from redis/DOC-738
Update persistent-ephemeral-storage.md
2 parents 8e0f07b + 029acce commit 9764005

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

content/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ toc: 'true'
1212
weight: 50
1313
---
1414
For each node in the cluster, you can configure paths for both persistent
15-
storage and ephemeral storage.
15+
storage and ephemeral storage. To do so, the volume must have full permissions for user and group `redislabs` or users:group `redislabs:redislabs`. See the [Customize system user and group]({{< relref "/operate/rs/installing-upgrading/install/customize-user-and-group" >}}) page for instructions.
1616

1717
{{< note >}}
1818
The persistent storage and ephemeral storage discussed in this document are not related
@@ -22,12 +22,11 @@ to Redis persistence or AWS ephemeral drives.
2222
## Persistent storage
2323

2424
Persistent storage is mandatory. The cluster uses persistent storage to store
25-
information that needs to persist even if a shard or a node fails,
25+
information that needs to persist if a shard or a node fails,
2626
such as server logs, configurations, and files.
2727

28-
For example, if you configure [persistence]({{< relref "/operate/rs/databases/configure/database-persistence.md" >}})
29-
for a database,
30-
then the persistence information is stored in this location.
28+
To set the frequency of syncs, you can configure [persistence]({{< relref "/operate/rs/databases/configure/database-persistence" >}})
29+
options for a database.
3130

3231
The persistent volume must be a storage area network (SAN)
3332
using an EXT4 or XFS file system and be connected as an external storage volume.
@@ -47,10 +46,10 @@ Ephemeral storage must be a locally attached volume on each node.
4746
For disk size requirements, see:
4847

4948
- [Hardware
50-
requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}})
49+
requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}})
5150
for general guidelines regarding the ideal disk size for each type of
52-
storage
51+
storage.
5352
- [Disk size requirements for extreme write
54-
scenarios]({{< relref "/operate/rs/clusters/optimize/disk-sizing-heavy-write-scenarios.md" >}})
53+
scenarios]({{< relref "/operate/rs/clusters/optimize/disk-sizing-heavy-write-scenarios" >}})
5554
for special considerations when dealing with a high rate of write
56-
commands
55+
commands.

0 commit comments

Comments
 (0)