[Bugs] [Bug 1797869] New: bitrot: Number of signing process threads should be configurable.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1797869

            Bug ID: 1797869
           Summary: bitrot: Number of signing process threads should be
                    configurable.
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: bitrot
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community
      Docs Contact: bugs at gluster.org



Description of problem:
The number of signing process threads (glfs_brpobj) should be configurable.
It's usually set to number of cores available. The default is set to 4.

[root at f281 glusterfs]# ps -ef | grep bitd
root      4318     1  1 10:48 ?        00:00:00 /usr/local/sbin/glusterfs -s
localhost --volfile-id gluster/bitd -p /var/run/gluster/bitd/bitd.pid -l
/var/log/glusterfs/bitd.log -S /var/run/gluster/9c52a5821a6a68c0.socket
--global-timer-wheel


[root at f281 glusterfs]# ps -eL | grep 4318
 4318  4318 ?        00:00:00 glusterfs
 4318  4319 ?        00:00:00 glfs_timer
 4318  4320 ?        00:00:00 glfs_sigwait
 4318  4321 ?        00:00:00 glfs_memsweep
 4318  4322 ?        00:00:00 glfs_sproc0
 4318  4323 ?        00:00:00 glfs_sproc1
 4318  4324 ?        00:00:00 glusterfs
 4318  4325 ?        00:00:00 glfs_epoll000
 4318  4326 ?        00:00:00 glfs_epoll001
 4318  4327 ?        00:00:00 glfs_tbfclock
 4318  4328 ?        00:00:00 glfs_clogjan
 4318  4329 ?        00:00:00 glfs_brpobj
 4318  4330 ?        00:00:00 glfs_brpobj
 4318  4331 ?        00:00:00 glfs_brpobj
 4318  4332 ?        00:00:00 glfs_brpobj
 4318  4333 ?        00:00:00 glfs_brhevent
 4318  4334 ?        00:00:00 glfs_clogcbki
 4318  4336 ?        00:00:00 glfs_clogcbki
 4318  4340 ?        00:00:00 glfs_clogcbki

Version-Release number of selected component (if applicable):
mainline

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.