[Bugs] [Bug 1317482] Different epoch values for each of NFS-Ganesha heads

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1317482



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13716 committed in release-3.7 by Kaleb
KEITHLEY (kkeithle at redhat.com) 
------
commit 3e5445ae7d1dbbcc138374b6d2e5f95ffc556f4b
Author: Soumya Koduri <skoduri at redhat.com>
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: 1317482
    Signed-off-by: Soumya Koduri <skoduri at redhat.com>
    Reviewed-on: http://review.gluster.org/13716
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan at redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9TdlvsVPg5&a=cc_unsubscribe