Bug 1317902 - Different epoch values for each of NFS-Ganesha heads
Summary: Different epoch values for each of NFS-Ganesha heads
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: ganesha-nfs
Version: mainline
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Soumya Koduri
QA Contact:
URL:
Whiteboard:
Depends On: 1242358 1317482
Blocks: 1188184
TreeView+ depends on / blocked
 
Reported: 2016-03-15 13:15 UTC by Soumya Koduri
Modified: 2016-06-16 14:00 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1317482
Environment:
Last Closed: 2016-06-16 14:00:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-03-15 13:17:02 UTC
REVIEW: http://review.gluster.org/13744 (ganesha: Include a script to generate epoch value) posted (#1) for review on master by soumya k (skoduri)

Comment 2 Vijay Bellur 2016-03-21 08:15:09 UTC
COMMIT: http://review.gluster.org/13744 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 9879c4e543e37de753b2650ab6fcd427afb0169d
Author: Soumya Koduri <skoduri>
Date:   Mon Mar 14 16:36:33 2016 +0530

    ganesha: Include a script to generate epoch value
    
    In a NFS-Ganesha HA cluster setup, for NFS clients to recover state
    succesfully post failover, the NFS-servers should start with a unique
    epoch value.
    
    With NFS-Ganesha 2.3, the service accepts an option "EPOCH_EXEC" which
    takes path of the script, generating epoch value. This script is executed before
    starting nfs-ganesha service so that the generated epoch value is used
    while bringing up the service.
    
    This patch includes the script to be used by nfs-ganesha+gluster setup.
    
    The epoch value is computed as follows -
           - first 32-bit contains the now() time
           - rest 32-bit value contains the local glusterd node uuid
    
    Change-Id: I876ea5a3730d7c6b40503e0fec16a4a142c54a36
    BUG: 1317902
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/13744
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: jiffin tony Thottan <jthottan>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 3 Niels de Vos 2016-06-16 14:00:28 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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