Bug 773600 - provide a way to start nfs server and self-heal daemon with valgrind
Summary: provide a way to start nfs server and self-heal daemon with valgrind
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: unclassified
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-01-12 11:50 UTC by Raghavendra Bhat
Modified: 2013-07-24 17:47 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:47:36 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: glusterfs-3.3.0qa40
Embargoed:


Attachments (Terms of Use)

Description Raghavendra Bhat 2012-01-12 11:50:35 UTC
Description of problem:

Currently glusterd has a option which if provided while starting the process or as an option in the volfile, then glusterd starts all the bricks with valgrind. But nfs server and the self-heal daemons are started in the normal mode only. When valgrind option is provided to glusterd, it should start nfs server and the self-heal daemon also with valgrind only along with the brick processes.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2012-02-15 03:18:31 UTC
CHANGE: http://review.gluster.com/2638 (mgmt/glusterd: changes to run nfs server and self-heal daemon with valgrind) merged in master by Vijay Bellur (vijay)

Comment 2 Raghavendra Bhat 2012-05-10 10:48:15 UTC
Checked with glusterfs-3.3.0qa40. If glusterd is run with the option (glusterd --xlator-option *.run-with-valgrind=yes), then all the processes started by glusterd such as glusterfsd, nfs server and self-heal-daemon (if the volume is replicate) are started in valgrind mode.


Note You need to log in before you can comment on or make changes to this bug.