diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2018-02-14 12:15:53 +0530 |
|---|---|---|
| committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2018-03-16 13:39:18 +0000 |
| commit | 721ba8f8075a6a5696f165282f1ef5742c1f4a46 (patch) | |
| tree | 8b71afabc12699821625bb39f5d820a1bd524882 /glusterfs.spec.in | |
| parent | 8fb21afdd033c5d466854400c6a7604fcf5241c3 (diff) | |
glusterd: volume get fixes for client-io-threads & quorum-type
1. If a replica volume created on glusterfs-3.8 was upgraded to
glusterfs-3.12, `gluster vol get volname client-io-threads` displayed
'on' even though it wasn't and the xlator wasn't loaded on
the client-graph. This was due to removing certain checks in
glusterd_get_default_val_for_volopt as a part of commit
47604fad4c2a3951077e41e0c007ceb979bb2c24. Fix it.
2. Also, as a part of op-version bump-up, client-io-threads was being
loaded on the clients during volfile regeneration. Prevent it.
3. AFR assumes quorum-type to be auto in newly created replic 3 (odd
replica in general) volumes but `gluster vol get quorum-type` displays
'none'. Fix it.
Change-Id: I19e586361ed1065c70fb378533d3b4dac1095df9
BUG: 1552404
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
(cherry picked from commit bd2c45fe3180fe36b042d5eabd348b6eaeb8d3e2)
Diffstat (limited to 'glusterfs.spec.in')
0 files changed, 0 insertions, 0 deletions