Bug 783980

Summary:	large value of bs*count in volume top write-perf/read-perf blocks glusterd
Product:	[Community] GlusterFS	Reporter:	M S Vishwanath Bhat <vbhat>
Component:	unclassified	Assignee:	Kaushal <kaushal>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	gluster-bugs, mzywusko
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-30 13:17:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description M S Vishwanath Bhat 2012-01-23 12:44:44 UTC

Description of problem:
For gluster volume top read-perf/write-perf when the value of bs*count is large, it blocks glusterd.

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

How reproducible:
always

Steps to Reproduce:
1. run volume top read-perf with large value of bs and count (bs*count should be alrge)
  
Actual results:
glusterd gets blocked and return after sometime with non-zero exit status. Now the subsequent gluster operations will fail.

Expected results:
glusterd should not get blocked. There should either be a limit on the bs*count value or the task should be performed in a different thread. 

Additional info:
This actually is a duplicate of bug https://bugzilla.redhat.com/show_bug.cgi?id=GLUSTER-2720. A patch was sent to this but that doesn't solve the issue. I couldn't reopen that bug so opening a new bug.

Comment 1 Anand Avati 2012-02-21 10:49:03 UTC

CHANGE: http://review.gluster.com/2761 (cli, glusterfsd: Fixes for "volume top {read,write}-perf") merged in master by Vijay Bellur (vijay)

Comment 2 M S Vishwanath Bhat 2012-04-30 13:15:40 UTC

Now there is limit on the size of "bs * count" value which is 10GB. So write-perf won't block glusterd.


[root@QA-29 vishwa]# gluster v top hosdu write-perf bs 2789473574385746754678576 count 100 list-cnt 10
'bs * count' value 429496729500 is greater than maximum allowed value of 10GB
Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir [nfs]] |[read-perf|write-perf [nfs|{bs <size> count <count>}]]}  [brick <brick>] [list-cnt <count>]