[Bugs] [Bug 1257546] New: [Backup]: Glusterfind list shows the session as corrupted on the peer node
bugzilla at redhat.com
bugzilla at redhat.com
Thu Aug 27 10:10:03 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1257546
Bug ID: 1257546
Summary: [Backup]: Glusterfind list shows the session as
corrupted on the peer node
Product: GlusterFS
Version: 3.7.3
Component: glusterfind
Severity: medium
Assignee: bugs at gluster.org
Reporter: avishwan at redhat.com
QA Contact: bugs at gluster.org
CC: avishwan at redhat.com, bugs at gluster.org,
khiremat at redhat.com, mchangir at redhat.com,
nsathyan at redhat.com, sanandpa at redhat.com
Depends On: 1232569, 1243838
Blocks: 1223636
+++ This bug was initially created as a clone of Bug #1243838 +++
+++ This bug was initially created as a clone of Bug #1232569 +++
Description of problem:
When a glusterfind session is created on one of the nodes, glusterfind list
displays the healthy state of the session. However, on the peer node, it tries
to open the status file at the $GLUSTERD_WORKDIR, not finding which, updates
the state of the session as 'corrupted'.
The error displayed in the logs (at the peer node where it shows as failed):
[2015-06-17 15:15:24,124] ERROR [utils - 152:fail] - Error Opening Session file
/var/lib/glusterd/glusterfind/sessn4/nash/status: [Errno 2] No such file or
directory: '/var/lib/glusterd/glusterfind/sessn4/nash/status'
Version-Release number of selected component (if applicable):
glusterfs-3.7.1-3.el6rhs.x86_64
How reproducible: Always
Steps to Reproduce:
1. Have a >=2 node cluster, with a volume (of any type), say 'vol1'
2. Create a glusterfind session from node1 and verify the output of glusterfind
list
3. Type the same command 'glusterfind list' on the peer node(s) and verify the
output
Actual results:
On the peer node, step3 displays the session as 'corrupted'
Expected results:
The state of the glusterfind session should be displayed as healthy when viewed
from any of the peer node
Additional info:
[root at dhcp43-93 ~]#
[root at dhcp43-93 ~]# glusterfind list
SESSION VOLUME SESSION TIME
---------------------------------------------------------------------------
sessn2 nash 2015-06-16 20:17:24
sessn3 nash 2015-06-16 17:47:02
sessp1 pluto 2015-06-16 21:15:06
sesso1 ozone 2015-06-15 23:48:42
sessn1 nash 2015-06-16 18:02:11
sessp2 pluto 2015-06-16 21:12:53
[root at dhcp43-93 ~]# gluster v list
nash
[root at dhcp43-93 ~]# glusterfind create sessn4 nash
Failed to set volume option build-pgfid on: volume set: failed: One or more
connected clients cannot support the feature being set. These clients need to
be upgraded or disconnected before running this command again
[root at dhcp43-93 ~]# glusterfind create sessn4 nash
Session sessn4 created with volume nash
[root at dhcp43-93 ~]#
[root at dhcp43-93 ~]#
[root at dhcp43-93 ~]# glusterfind list
SESSION VOLUME SESSION TIME
---------------------------------------------------------------------------
sessn2 nash 2015-06-16 20:17:24
sessn3 nash 2015-06-16 17:47:02
sessp1 pluto 2015-06-16 21:15:06
sessn4 nash 2015-06-17 15:14:18
sesso1 ozone 2015-06-15 23:48:42
sessn1 nash 2015-06-16 18:02:11
sessp2 pluto 2015-06-16 21:12:53
[root at dhcp43-93 ~]# ls /var/lib/glusterd/glusterfind/
.keys/ sessn1/ sessn2/ sessn3/ sessn4/ sesso1/ sesso2/ sesso3/ sessp1/ sessp2/
sessv1/
[root at dhcp43-93 ~]# ls /var/lib/glusterd/glusterfind/sessn4/nash/
%2Frhs%2Fthinbrick1%2Fnash.status %2Frhs%2Fthinbrick2%2Fnash.status
sessn4_nash_secret.pem sessn4_nash_secret.pem.pub status
[root at dhcp43-93 ~]# ls /var/lib/glusterd/glusterfind/sessn4/nash/^C
[root at dhcp43-93 ~]# ls /var/lib/glusterd/glusterfind/
.keys/ sessn1/ sessn2/ sessn3/ sessn4/ sesso1/ sesso2/ sesso3/ sessp1/ sessp2/
sessv1/
[root at dhcp43-93 ~]# ls /var/lib/glusterd/glusterfind/sessn4/nash/
%2Frhs%2Fthinbrick1%2Fnash.status %2Frhs%2Fthinbrick2%2Fnash.status
sessn4_nash_secret.pem sessn4_nash_secret.pem.pub status
[root at dhcp43-93 ~]# ls /var/log/glusterfs/glusterfind/
cli.log nash/ sess21/ sessn1/ sessn2/ sessn3/ sessn4/ sesso1/ sesso2/
sesso3/ sessp1/ sessp2/ sessv1/
[root at dhcp43-93 ~]# vi /var/log/glusterfs/glusterfind/sessn4/nash/cli.log
############### peer node ########################3
[root at dhcp43-155 ~]#
[root at dhcp43-155 ~]# # after creating a new session 'sessn4'
[root at dhcp43-155 ~]#
[root at dhcp43-155 ~]#
[root at dhcp43-155 ~]# glusterfind list
SESSION VOLUME SESSION TIME
---------------------------------------------------------------------------
sessp1 pluto Session Corrupted
sessn3 nash Session Corrupted
sessp2 pluto Session Corrupted
sessn4 nash Session Corrupted
sessn2 nash Session Corrupted
sessn1 nash Session Corrupted
sesso1 ozone Session Corrupted
[root at dhcp43-155 ~]# vi /var/log/glusterfs/glusterfind/
cli.log sessn1/ sessn2/ sesso1/ sessp1/ sessp2/
[root at dhcp43-155 ~]# glusterfind pre sessn4 nash /tmp/outn.txt
Error Opening Session file /var/lib/glusterd/glusterfind/sessn4/nash/status:
[Errno 2] No such file or directory:
'/var/lib/glusterd/glusterfind/sessn4/nash/status'
[root at dhcp43-155 ~]# ls /var/lib/glusterd/glusterfind/
.keys/ sessn1/ sessn2/ sessn3/ sessn4/ sesso1/ sesso2/ sesso3/ sessp1/ sessp2/
sessv1/
[root at dhcp43-155 ~]# ls
/var/lib/glusterd/glusterfind/sessn4/nash/%2Frhs%2Fthinbrick
%2Frhs%2Fthinbrick1%2Fnash.status %2Frhs%2Fthinbrick2%2Fnash.status
[root at dhcp43-155 ~]# ls
/var/lib/glusterd/glusterfind/sessn4/nash/%2Frhs%2Fthinbrick^C
[root at dhcp43-155 ~]# ls /var/log/glusterfs/glusterfind/sessn4/nash/
cli.log
[root at dhcp43-155 ~]# vi /var/log/glusterfs/glusterfind/sessn4/nash/cli.log
[root at dhcp43-155 ~]# rpm -qa | grep glustefs
[root at dhcp43-155 ~]# rpm -qa | grep glusterfs
glusterfs-api-3.7.1-3.el6rhs.x86_64
glusterfs-libs-3.7.1-3.el6rhs.x86_64
glusterfs-3.7.1-3.el6rhs.x86_64
glusterfs-fuse-3.7.1-3.el6rhs.x86_64
glusterfs-server-3.7.1-3.el6rhs.x86_64
glusterfs-client-xlators-3.7.1-3.el6rhs.x86_64
glusterfs-cli-3.7.1-3.el6rhs.x86_64
[root at dhcp43-155 ~]#
--- Additional comment from Aravinda VK on 2015-07-16 08:50:50 EDT ---
glusterfind commands will not work in peer nodes other than the initiated node.
We need to enhance glusterfind to use Meta volume to save status files and
collect pem keys from all nodes and distribute to all Nodes of cluster. With
this enhancement, we can run glusterfind command from any peer node
--- Additional comment from Anand Avati on 2015-07-16 09:11:19 EDT ---
REVIEW: http://review.gluster.org/11699 (tools/glusterfind: Do not show session
corrupted if no status file) posted (#1) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Anand Avati on 2015-08-27 02:28:26 EDT ---
REVIEW: http://review.gluster.org/11699 (tools/glusterfind: Do not show session
corrupted if no status file) posted (#4) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Anand Avati on 2015-08-27 06:08:31 EDT ---
COMMIT: http://review.gluster.org/11699 committed in master by Venky Shankar
(vshankar at redhat.com)
------
commit cf3d6f14ae031ba2f5269cea6dbf80e60d00cce5
Author: Aravinda VK <avishwan at redhat.com>
Date: Thu Jul 16 18:23:36 2015 +0530
tools/glusterfind: Do not show session corrupted if no status file
When a glusterfind session is created it creates session directories
in all the nodes which are part of the Volume. But session status
file only present in initiated node.
Show Session corrupted only if status file exists and invalid content.
Change-Id: I8443c0335b872645b54c0aa77d9893dbe2589c92
Signed-off-by: Aravinda VK <avishwan at redhat.com>
BUG: 1243838
Reviewed-on: http://review.gluster.org/11699
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Milind Changire <mchangir at redhat.com>
Reviewed-by: Kotresh HR <khiremat at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1223636
[Bug 1223636] 3.1 QE Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1232569
[Bug 1232569] [Backup]: Glusterfind list shows the session as corrupted on
the peer node
https://bugzilla.redhat.com/show_bug.cgi?id=1243838
[Bug 1243838] [Backup]: Glusterfind list shows the session as corrupted on
the peer node
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list