Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1065049 - Volume set command "cluster.heal-timeout" not setting the value in vol files
Summary: Volume set command "cluster.heal-timeout" not setting the value in vol files
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-13 18:41 UTC by Lalatendu Mohanty
Modified: 2014-02-14 09:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-14 09:22:51 UTC


Attachments (Terms of Use)

Description Lalatendu Mohanty 2014-02-13 18:41:02 UTC
Description of problem:

Volume set command "cluster.heal-timeout <value>" should set the value in client and nfs vol files. But after the heal-timeout value is only can be seen in "gluster v info <Volume>" but not in client and nfs vol files

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.59rhs-1.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a replicated volume
2. run "gluster volume set <volumename> cluster.heal-timeout 61"
3. Check "gluster v info <volumename>" and volfiles in /var/lib/glusterd/vols/ and /var/lib/glusterd/nfs

Actual results:

There is no information on "heal-timeout 61" in the vol files

Expected results:

The information about "heal-timeout" should be there in the vol files

Additional info:

# gluster v info smb-vol-2
 
Volume Name: smb-vol-2
Type: Distributed-Replicate
Volume ID: 15352e5c-37a7-477c-80f4-fd071f7827c8
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.37.133:/rhs/brick1/smb-vol-2-b1
Brick2: 10.70.37.160:/rhs/brick1/smb-vol-2-b1
Brick3: 10.70.37.210:/rhs/brick1/smb-vol-2-b2
Brick4: 10.70.37.133:/rhs/brick2/smb-vol-2-b2
Options Reconfigured:
performance.strict-o-direct: enable
cluster.heal-timeout: 61
cluster.entry-self-heal: yes
cluster.entry-change-log: enable
cluster.ensure-durability: off
cluster.eager-lock: off
cluster.data-self-heal: no
cluster.data-change-log: 0
cluster.choose-local: 1
cluster.background-self-heal-count: 5


CLient volfile: var/lib/glusterd/vols/smb-vol-2/smb-vol-2-fuse.vol
NFS vol file: /var/lib/glusterd/nfs/nfs-server.vol

Comment 1 Lalatendu Mohanty 2014-02-14 09:22:51 UTC
I was not aware that value of heal-timeout should be in  selfheal vol file and not in client and NFS vol files.

Checked the self-heal vol file and found the option heal-timeout set to correct value. Hence closing the bug.

/var/lib/glusterd/glustershd/glustershd-server.vol 

volume smb-vol-2-replicate-1
    type cluster/replicate
    option iam-self-heal-daemon yes
    option heal-timeout 61
    option self-heal-daemon no
    option ensure-durability off
    option choose-local 1
    option eager-lock off
    option metadata-change-log on
    option data-change-log 0
    option entry-self-heal on
    option data-self-heal on
    option metadata-self-heal on
    option background-self-heal-count 0
    option entry-change-log enable
    subvolumes smb-vol-2-client-2 smb-vol-2-client-3
end-volume


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