Bug 1419436 - [Nfs-Ganesha] Ganesha cluster not goes to "in grace" period, during second node failback.
Summary: [Nfs-Ganesha] Ganesha cluster not goes to "in grace" period, during second no...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: common-ha
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Kaleb KEITHLEY
QA Contact: Arthy Loganathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-06 07:19 UTC by Arthy Loganathan
Modified: 2017-08-21 17:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-21 17:40:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Arthy Loganathan 2017-02-06 07:19:42 UTC
Description of problem:
Ganesha cluster not goes to "in grace" period, during second node failback.

I have observed this behaviour only once. So raised this bug for tracking purpose.
And If this issue is seen again, will raise the priority of the bug.

Version-Release number of selected component (if applicable):
nfs-ganesha-gluster-2.4.1-6.el7rhgs.x86_64
nfs-ganesha-2.4.1-6.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-12.el7rhgs.x86_64


How reproducible:
Once

Steps to Reproduce:
1. Create a 4 node ganesha cluster.
2. Create a volume and enable ganesha on it.
3. Run IOs.
4. Reboot two nodes node1 and node2. [ganesha cluster will go to stopped state]
5. Once failover happened and IO's starts running, start nfs-ganesha in node1.
6, Start nfs-ganesha in node2.

Actual results:
Ganesha cluster not goes to "in grace" period, during second node failback and IO's are not getting paused for 90 seconds.

Expected results:
Ganesha cluster should go to grace period and after coming out of grace, IO should be running.

Additional info:


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