Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1474639

Summary:	[Scale] : Rebalance Logs are bulky.
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, asoman, bugs, nbalacha, rcyriac, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.13.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1473259
Clones:	1475662 (view as bug list)		Environment:
Last Closed:	2017-12-08 17:35:17 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:
Bug Depends On:	1473259
Bug Blocks:	1475662

Comment 1 Susant Kumar Palai 2017-07-25 06:07:12 UTC

Description:
  Every time all the thread sleeps or wakes up, we log a message about that event. 
Sometime this can be noisy where the number of files eligible to be migrated are placed far away from each other.

log instances:
[2017-07-20 03:47:00.891430] I [dht-rebalance.c:2858:gf_defrag_task] 0-DHT: Thread sleeping. current thread count: 2
[2017-07-20 03:47:00.891484] I [dht-rebalance.c:2858:gf_defrag_task] 0-DHT: Thread sleeping. current thread count: 2
[2017-07-20 03:47:00.891525] I [dht-rebalance.c:2858:gf_defrag_task] 0-DHT: Thread sleeping. current thread count: 2
[2017-07-20 03:47:00.892125] I [dht-rebalance.c:2858:gf_defrag_task] 0-DHT: Thread sleeping. current thread count: 2
[2017-07-20 03:47:00.892197] I [dht-rebalance.c:2858:gf_defrag_task] 0-DHT: Thread sleeping. current thread count: 2
[2017-07-20 03:47:00.913433] I [dht-rebalance.c:2858:gf_defrag_task] 0-DHT: Thread sleeping. current thread count: 2

Comment 2 Worker Ant 2017-07-25 06:15:31 UTC

REVIEW: https://review.gluster.org/17866 (cluster/dht: change log level to debug for thread activity) posted (#1) for review on master by Susant Palai (spalai)

Comment 3 Worker Ant 2017-07-26 05:06:06 UTC

REVIEW: https://review.gluster.org/17866 (cluster/dht: change log level to debug for thread activity) posted (#2) for review on master by Susant Palai (spalai)

Comment 4 Worker Ant 2017-07-26 21:50:26 UTC

COMMIT: https://review.gluster.org/17866 committed in master by Jeff Darcy (jeff.us) 
------
commit 302aaeeddc64cd31997a4965b81ba772cd1b36c6
Author: Susant Palai <spalai>
Date:   Tue Jul 25 11:43:37 2017 +0530

    cluster/dht: change log level to debug for thread activity
    
      Every time all the thread sleeps or wakes up, we log a message
    about that event. Sometime this can be noisy where the number of
    files eligible to be migrated are placed far away from each other.
    
    Moving the logs to DEBUG.
    
    Change-Id: I4dc2cc9fdf4f42d4001754532a5bc4aeb3f0f959
    BUG: 1474639
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: https://review.gluster.org/17866
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Amar Tumballi <amarts>
    Reviewed-by: N Balachandran <nbalacha>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 5 Shyamsundar 2017-12-08 17:35:17 UTC

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.13.0, please open a new bug report.

glusterfs-3.13.0 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] http://lists.gluster.org/pipermail/announce/2017-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/