[Bugs] [Bug 1414750] New: [Geo-rep] Slave mount log file is cluttered by logs of multiple active mounts
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jan 19 11:16:31 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1414750
Bug ID: 1414750
Summary: [Geo-rep] Slave mount log file is cluttered by logs of
multiple active mounts
Product: Red Hat Gluster Storage
Version: 3.1
Component: geo-replication
Severity: high
Assignee: avishwan at redhat.com
Reporter: khiremat at redhat.com
QA Contact: rhinduja at redhat.com
CC: avishwan at redhat.com, bugs at gluster.org,
csaba at redhat.com, rhs-bugs at redhat.com,
storage-qa-internal at redhat.com
Depends On: 1412689
+++ This bug was initially created as a clone of Bug #1412689 +++
Description of problem:
Slave mount log file is cluttered by logs of multiple active mounts
Geo-rep worker mounts the slave volume on the slave
node. If multiple worker connects to same slave node,
all workers share the same mount log file. This
is very difficult to debug as logs are cluttered from
different mounts
The location of log file is
/var/log/glusterfs/geo-replication-slaves/*.gluster.log
Version-Release number of selected component (if applicable):
mainline
How reproducible:
Always
Steps to Reproduce:
1. Create master volume with two bricks
2. Create slave volume with single brick
3. Establish geo-rep sessio between them.
6. Now geo-rep will have two slave mounts per master brick. Both will log into
single file.
Actual results:
Multiple mount logs to same file
Expected results:
Each mount should log to separate file
Additional info:
--- Additional comment from Worker Ant on 2017-01-12 09:57:57 EST ---
REVIEW: http://review.gluster.org/16384 (geo-rep: Separate slave mount logs for
each connection) posted (#1) for review on master by Kotresh HR
(khiremat at redhat.com)
--- Additional comment from Aravinda VK on 2017-01-12 23:49:56 EST ---
--- Additional comment from Worker Ant on 2017-01-18 03:47:05 EST ---
COMMIT: http://review.gluster.org/16384 committed in master by Aravinda VK
(avishwan at redhat.com)
------
commit ff5e91a60887d22934fcb5f8a15dd36019d6e09a
Author: Kotresh HR <khiremat at redhat.com>
Date: Tue Jan 10 15:39:55 2017 -0500
geo-rep: Separate slave mount logs for each connection
Geo-rep worker mounts the slave volume on the slave
node. If multiple worker connects to same slave node,
all workers share the same mount log file. This
is very difficult to debug as logs are cluttered from
different mounts. Hence creating separate mount log
file for each connection from worker. Each connection
from worker is identified uniquely using 'mastervol uuid',
'master host', 'master brickpath', 'salve vol'. The log
file name will be combination of the above.
Change-Id: I67871dc8e8ea5864e2ad55e2a82063be0138bf0c
BUG: 1412689
Signed-off-by: Kotresh HR <khiremat at redhat.com>
Reviewed-on: http://review.gluster.org/16384
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Aravinda VK <avishwan at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1412689
[Bug 1412689] [Geo-rep] Slave mount log file is cluttered by logs of
multiple active mounts
--
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=3cRdkD6hUg&a=cc_unsubscribe
More information about the Bugs
mailing list