Bug 1335070 - change the misleading multi threaded self heal option
Summary: change the misleading multi threaded self heal option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: replicate
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Pranith Kumar K
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-11 09:35 UTC by Nag Pavan Chilakam
Modified: 2019-04-03 09:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-01 11:42:38 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.