Bug 1335070

Summary: change the misleading multi threaded self heal option
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: medium Docs Contact:
Priority: low    
Version: rhgs-3.1CC: ravishankar, rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-01 11:42:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nag Pavan Chilakam 2016-05-11 09:35:20 UTC 
The cluster.shd-max-threads option is misleading as it actually has nothing to do with the threads the admin can desire to spawn.
It is more of the number of parallel files that can be getting healed at any particular time.
Hence change the option to something like cluster.shd-max-parallel-files or something more appropriate

version:
glusterfs-geo-replication-3.7.9-4.el6rhs.x86_64
python-gluster-3.7.1-17.el6rhs.11.hotfix.sfdc01581565.x86_64
glusterfs-libs-3.7.9-4.el6rhs.x86_64
glusterfs-client-xlators-3.7.9-4.el6rhs.x86_64
glusterfs-fuse-3.7.9-4.el6rhs.x86_64
glusterfs-server-3.7.9-4.el6rhs.x86_64
glusterfs-api-devel-3.7.9-4.el6rhs.x86_64
glusterfs-rdma-3.7.9-4.el6rhs.x86_64
glusterfs-api-3.7.9-4.el6rhs.x86_64
glusterfs-devel-3.7.9-4.el6rhs.x86_64
glusterfs-debuginfo-3.7.9-4.el6rhs.x86_64