Bug 764700 (GLUSTER-2968)

Summary:	command-line arguments should override vol config
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	logging	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	anush, gluster-bugs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joe Julian 2011-05-31 21:38:58 UTC

I like to mount a client with a specific log-level instead of changing the whole cluster when I want to debug a problem.

For instance, I may want to:
  mount -o log-level=TRACE ewcs2:sharedvol1 /mnt/test

Which works until the vol file for sharedvol1 is processed and log-level INFO is encountered.

Please make the command-line arguments override the vol file settings. This should be true for all executables.

Comment 1 Amar Tumballi 2011-06-01 07:29:41 UTC

JoeJulian, Let me evaluate the possibilities of it.

Comment 2 Amar Tumballi 2011-06-07 06:03:28 UTC

Noticed that the '--xlator-options' command line arguments overwrites the volume file options. But its currently not the case for '--log-level'.

Patch submitted at http://patches.gluster.com/patch/7393/

Comment 3 Amar Tumballi 2011-06-21 02:22:59 UTC

Hi Joe,

We decided not to take this patch in, as if we allow this. after a period, we can not set the option back to anything else even if we want to without a remount (ie, restarting 'glusterfs' process).

As of now, the behavior of retaining the command line argument as long as a explicit gluster cli volume set is issued seems fine for us. 

I will be closing it with 'Wont fix'. Please re-open if it is very necessary.

-Amar

Comment 4 Joe Julian 2011-06-21 02:47:05 UTC

I'm not reopening as it's just an annoyance, not a need, but...

If log-level is specified on the command line, I would expect the behavior you identified: cannot change the option back without a remount. In my particular case, that's the behavior I would desire. If I didn't want that behavior, I would mount without specifying an override.