Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1598416 - client-io-threads option not working for replicated volumes
client-io-threads option not working for replicated volumes
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: replicate (Show other bugs)
3.3
x86_64 Linux
high Severity high
: ---
: RHGS 3.3.1 Async
Assigned To: Ravishankar N
Vijay Avuthu
: Performance, ZStream
Depends On: 1499158
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-05 08:04 EDT by Atin Mukherjee
Modified: 2018-07-20 02:17 EDT (History)
11 users (show)

See Also:
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.
Story Points: ---
Clone Of: 1487495
Environment:
Last Closed: 2018-07-19 02:00:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2222 None None None 2018-07-19 02:00 EDT

  None (edit)
Comment 9 Vijay Avuthu 2018-07-11 01:46:05 EDT
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 10:29:51 EDT
> 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 02:00:10 EDT
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.