Bug 1598416 - client-io-threads option not working for replicated volumes
Summary: client-io-threads option not working for replicated volumes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: replicate
Version: rhgs-3.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Ravishankar N
QA Contact: Vijay Avuthu
URL:
Whiteboard:
Depends On: 1499158
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-05 12:04 UTC by Atin Mukherjee
Modified: 2018-07-20 06:17 UTC (History)
11 users (show)

Fixed In Version: glusterfs-3.8.4-54.14
Doc Type: Bug Fix
Doc Text:
Previously, due to a bug in glusterd, executing the `gluster volume set <volname> client-io-threads on` command on a replicate volume returned success without actually enabling it in the client graph. This updates fixes that bug, and executing the `gluster volume set <volname> client-io-threads on` command provides a correct success result and ensures that the translator is loaded on the client graph.
Clone Of: 1487495
Environment:
Last Closed: 2018-07-19 06:00:10 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2222 None None None 2018-07-19 06:00:49 UTC

Comment 9 Vijay Avuthu 2018-07-11 05:46:05 UTC
Update:
=========

Build used: glusterfs-3.8.4-54.14.el7rhgs.x86_64

> Verified the scenarios in comment 3 and working as expected.

Moving to verified.

Comment 12 Ravishankar N 2018-07-17 14:29:51 UTC
> Previously, due to a bug in glusterd, the client-io-threads translator was not loaded in a replicated volume. Hence, executing the `gluster volume set <volname> client-io-threads on` command returned an incorrect success result.


I don't think the 'Hence' is appropriate. The bug was not that client-io-threads translator was not loaded in a replicated volume by default. The problem was when you explicitly set it on, it returned success but still did not enable it/load it in the client graph.

Comment 18 errata-xmlrpc 2018-07-19 06:00:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2222


Note You need to log in before you can comment on or make changes to this bug.