REVIEW: http://review.gluster.org/15062 (dht/rebalance: allocate migrator thread pool dynamically) posted (#1) for review on release-3.7 by Susant Palai (spalai)
REVIEW: http://review.gluster.org/15062 (dht/rebalance: allocate migrator thread pool dynamically) posted (#2) for review on release-3.7 by Susant Palai (spalai)
REVIEW: http://review.gluster.org/15062 (dht/rebalance: allocate migrator thread pool dynamically) posted (#3) for review on release-3.7 by Susant Palai (spalai)
COMMIT: http://review.gluster.org/15062 committed in release-3.7 by Raghavendra G (rgowdapp) ------ commit 59378892641a10ba0268a044310264e52afe8ea0 Author: Susant Palai <spalai> Date: Thu Aug 4 12:31:24 2016 +0530 dht/rebalance: allocate migrator thread pool dynamically Problems: The maximum number of migratior threads created was static set to "40". And the number of these threads get created in rebalance depends on the number of cores user has. If the number of cores exceeds 40, a crash or memory corruption can be seen. Fix: Make the migratior thread pool dynamic. > Change-Id: Ifbdac8a1a396363dd75e2f6bcb454070cfdbf839 > BUG: 1362070 > Reviewed-on: http://review.gluster.org/15000 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Raghavendra G <rgowdapp> (cherry picked from commit b8e8bfc7e4d3eaf76bb637221bc6392ec10ca54b) Change-Id: Ifbdac8a1a396363dd75e2f6bcb454070cfdbf839 BUG: 1362070 Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/15062 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.15, please open a new bug report. glusterfs-3.7.15 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-devel/2016-September/050714.html [2] https://www.gluster.org/pipermail/gluster-users/