Back to bug 1381142

Who When What Removed Added
Daiji KANEMATSU 2016-10-06 00:46:03 UTC CC dkanemat
Nithya Balachandran 2016-10-13 09:19:24 UTC CC nbalacha, rhs-bugs, storage-qa-internal
Component glusterfs distribute
Assignee rhs-bugs nbalacha
QA Contact storage-qa-internal tdesala
Susant Kumar Palai 2016-10-13 09:48:55 UTC Status NEW ASSIGNED
CC spalai, tsugano
Assignee nbalacha spalai
Flags needinfo?(tsugano)
Bipin Kunal 2016-10-19 06:31:41 UTC Flags needinfo?(tsugano)
Version 3.2 3.1
CC bkunal
Mukul Malhotra 2016-10-19 07:16:32 UTC CC mmalhotr
Manoj Pillai 2016-10-24 17:57:50 UTC CC mpillai
Manoj Pillai 2016-11-02 08:22:09 UTC Flags needinfo?(spalai)
Susant Kumar Palai 2016-11-03 06:54:45 UTC Flags needinfo?(spalai)
Susant Kumar Palai 2016-11-04 07:18:00 UTC CC srangana
Flags needinfo?(srangana)
Shyamsundar 2016-11-13 23:44:06 UTC Flags needinfo?(srangana)
Atin Mukherjee 2016-11-14 04:07:47 UTC CC amukherj
Bipin Kunal 2016-11-29 07:37:17 UTC Flags needinfo?(spalai)
Susant Kumar Palai 2016-11-29 08:22:41 UTC Flags needinfo?(spalai)
Bipin Kunal 2016-12-20 12:30:23 UTC Blocks 1369781
Susant Kumar Palai 2017-01-24 11:35:56 UTC Flags needinfo?(mpillai)
Manoj Pillai 2017-01-30 06:01:26 UTC Flags needinfo?(mpillai)
Susant Kumar Palai 2017-02-08 02:11:28 UTC Blocks 1420166
Nithya Balachandran 2017-02-10 06:00:38 UTC Blocks 1417147
Atin Mukherjee 2017-02-20 13:02:05 UTC Status ASSIGNED POST
Susant Kumar Palai 2017-02-23 12:45:38 UTC Flags needinfo?(mpillai)
Atin Mukherjee 2017-02-23 14:50:54 UTC Blocks 1417145
Alok 2017-02-28 06:09:23 UTC CC asrivast
Rahul Hinduja 2017-02-28 10:39:44 UTC CC rhinduja
Manoj Pillai 2017-03-01 07:34:31 UTC Flags needinfo?(mpillai)
Red Hat Bugzilla Rules Engine 2017-03-01 07:34:37 UTC Target Release --- RHGS 3.3.0
Rejy M Cyriac 2017-05-17 08:31:07 UTC CC rcyriac
Nithya Balachandran 2017-05-18 17:08:06 UTC Status POST MODIFIED
errata-xmlrpc 2017-05-27 11:01:36 UTC Status MODIFIED ON_QA
Milind Changire 2017-05-27 11:14:58 UTC Fixed In Version glusterfs-3.8.4-26
Susant Kumar Palai 2017-07-14 12:30:47 UTC Doc Text Rebalance throttle configuration was limited to "lazy", "normal" and "aggressive" which depends on the number of cores. In some cases it was observed that there was no performance difference between "normal" and "aggressive" mode. In the process of debugging this, we found some bottlenecks in our thread management(synctasks) infra, which is fixed now. Plus rebalance throttle now can be configured by numbers which will represent the number of migration threads in rebalance. Max number depends on the number of cores in the machine.
Doc Type If docs needed, set a value Enhancement
Prasad Desala 2017-08-03 12:26:47 UTC QA Contact tdesala asoman
Ambarish 2017-08-04 03:53:17 UTC Status ON_QA VERIFIED
Laura Bailey 2017-08-15 06:57:19 UTC Doc Text Rebalance throttle configuration was limited to "lazy", "normal" and "aggressive" which depends on the number of cores. In some cases it was observed that there was no performance difference between "normal" and "aggressive" mode. In the process of debugging this, we found some bottlenecks in our thread management(synctasks) infra, which is fixed now. Plus rebalance throttle now can be configured by numbers which will represent the number of migration threads in rebalance. Max number depends on the number of cores in the machine. Rebalance throttling previously had three modes; however, two of these modes had similar performance because of bottlenecks in thread management. Rebalance throttling is now configured by specifying a number of migration threads to use instead of the previous lazy, normal, and aggressive modes.
Doc Type Enhancement Bug Fix
Flags needinfo?(spalai)
Susant Kumar Palai 2017-08-16 06:44:21 UTC Flags needinfo?(spalai)
Laura Bailey 2017-08-17 05:49:07 UTC Doc Text Rebalance throttling previously had three modes; however, two of these modes had similar performance because of bottlenecks in thread management. Rebalance throttling is now configured by specifying a number of migration threads to use instead of the previous lazy, normal, and aggressive modes. Rebalance throttling previously had three modes; however, two of these modes had similar performance because of bottlenecks in thread management. This has been corrected. In addition, rebalance throttling can now be configured by specifying a number of migration threads to use as well as with the previous lazy, normal, and aggressive modes.
Bipin Kunal 2017-08-24 09:50:25 UTC CC asoman
Flags needinfo?(asoman)
errata-xmlrpc 2017-09-21 00:55:16 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-09-21 04:28:23 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-09-21 00:28:23 UTC

Back to bug 1381142