Build used: glusterfs-3.8.4-54.14.el7rhgs.x86_64
> Verified the scenarios in comment 3 and working as expected.
Moving to verified.
> 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.
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.