How to set GlusterFS volume options

Changing a GlusterFS volume option adjusts how an existing volume serves clients, heals replicated data, writes logs, or handles directory and cache behavior. Treat each change as storage configuration because a wrong value can affect every client that mounts the volume.

The gluster volume set command stores one option key and value for a named volume through glusterd. The stored value is visible with gluster volume get, and the trusted pool distributes it to the volume's brick and client graph according to what the option controls.

Some options take effect immediately, while client-side translators and mount-time settings may require reconnecting clients before behavior changes. Change one key per maintenance note, check the previous value first, and avoid access, TLS, quorum, or self-heal changes until the expected client and redundancy impact is clear.

Steps to set GlusterFS volume options:

Open a terminal on a server in the trusted storage pool.
List volumes to confirm the target volume name.
```
$ sudo gluster volume list
volume1
```

Check the current value for the option key.

$ sudo gluster volume get volume1 performance.readdir-ahead
Option                                   Value
------                                   -----
performance.readdir-ahead                off

Use the exact option key from the volume option table or a change record.
Related: How to list GlusterFS volume options

Set one option value on the volume.
```
$ sudo gluster volume set volume1 performance.readdir-ahead on
volume set: success
```
Change one option per test window. Access rules such as auth.allow, TLS keys, quorum settings, and self-heal controls can block clients or change write availability when the value is wrong.

Verify the stored option value.

$ sudo gluster volume get volume1 performance.readdir-ahead
Option                                   Value
------                                   -----
performance.readdir-ahead                on

Reset a custom value with sudo gluster volume reset volume1 performance.readdir-ahead if the change causes a regression.

Check brick state after the option change.

$ sudo gluster volume status volume1
Status of volume: volume1
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick node1:/srv/gluster/brick1             55032     0          Y       4070

Task Status of Volume volume1
------------------------------------------------------------------------------
There are no active volume tasks

If the changed option affects client-side translators or mount-time behavior, reconnect affected clients before judging the new behavior.
Related: How to check GlusterFS volume status