gluster/glusterdocs
1
0
Fork 0
mirror of https://github.com/gluster/glusterdocs.git synced 2026-02-05 15:47:01 +01:00
Code Issues Releases Activity

docs/Administrator-Guide/arbiter-volumes-and-quorum.md: typo quorm

Browse Source
This commit is contained in:
Johannes Kastl
2022-05-12 14:20:35 +02:00
parent 672e6ca296
commit 133ce67063
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/Administrator-Guide/arbiter-volumes-and-quorum.md
View File

@@ -176,7 +176,7 @@ The following volume set options are used to configure it:
to specify the number of bricks to be active to participate in quorum.
If the quorum-type is auto then this option has no significance.
Earlier, when quorm was not met, the replica subvolume turned read-only. But
Earlier, when quorum was not met, the replica subvolume turned read-only. But
since [glusterfs-3.13](https://docs.gluster.org/en/latest/release-notes/3.13.0/#addition-of-checks-for-allowing-lookups-in-afr-and-removal-of-clusterquorum-reads-volume-option) and upwards, the subvolume becomes unavailable, i.e. all
the file operations fail with ENOTCONN error instead of becoming EROFS.
This means the ```cluster.quorum-reads``` volume option is also not supported.