[Bugs] [Bug 1213352] New: nfs-ganesha: HA issue, the iozone process is not moving ahead, once the nfs-ganesha is killed

[bugzilla at redhat.com]

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

            Bug ID: 1213352
           Summary: nfs-ganesha: HA issue, the iozone process is not
                    moving ahead, once the nfs-ganesha is killed
           Product: GlusterFS
           Version: 3.7.0
         Component: nfs
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: saujain at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
As per the HA functionality, the IO should resume after the grace period.
NOw we are providing nfs-ganesha cluster with HA functionality, so the IO that
is going should resume even in case the nfs-ganesha process is killed. This
should IO resumption should happen after the grace period completion, as the
failover would have happened to another node.

So, this is not happening for the present setup and it is a problem.

Version-Release number of selected component (if applicable):
nfs-ganesha-2.2-0.rc8.el6.x86_64
glusterfs-3.7dev-0.1017.git7fb85e3.el6.x86_64

How reproducible:
Tried HA for first time.

Steps to Reproduce:
1. do cluster setup for nfs-ganesha, as per guidelines
2. once the nfs-ganehsa is up, mount the volume on a client
3. start the  iozone
4. kill the nfs-ganesha process on the server node.


Actual results:
step 1. -- cluster done, nfs -ganesha come up only on 2 nodes out of four nodes

step 2. -- mount it done using vers=4,
step 3. -- iozone started
step 4. kill the nfs ganesha process using the kill command,

iozone stuck on mount point, not moving ahead


It is not moving ahead from this point.
Expected results:
IO should move ahead, as HA functionality should allow failover of the
nfs-ganesha process to the other node.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.