Bug 1215382 - Bricks fail to start with tiering related logs on the brick
Summary: Bricks fail to start with tiering related logs on the brick
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Niels de Vos
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1213125
Blocks: glusterfs-3.7.0 1260923
TreeView+ depends on / blocked
 
Reported: 2015-04-26 08:11 UTC by Niels de Vos
Modified: 2015-10-30 17:32 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.7.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1213125
Environment:
Last Closed: 2015-05-14 17:27:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Niels de Vos 2015-04-26 08:11:42 UTC
+++ This bug was initially created as a clone of Bug #1213125 +++

Description of problem:
Volume fails to start. 

Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. Create a volume and attempt to start it.
2.
3.

Actual results:
Volume fails to start. Bricks fail to start on the localhost.

[2015-04-18 17:06:51.310779] I [MSGID: 100030] [glusterfsd.c:2288:main] 0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/glusterfsd version 3.8dev (args: /usr/local/sbin/glusterfsd -s rhs1 --volfile-id testvol.rhs1.tmp-brick1 -p /var/lib/glusterd/vols/testvol/run/rhs1-tmp-brick1.pid -S /var/run/gluster/38b33304ed3bba0bb77e59883a8a91f4.socket --brick-name /tmp/brick1 -l /var/log/glusterfs/bricks/tmp-brick1.log --xlator-option *-posix.glusterd-uuid=3ae0f8b2-ae34-4a7d-b8ea-3afd27e1356c --brick-port 49152 --xlator-option testvol-server.listen-port=49152)
[2015-04-18 17:06:51.329406] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2015-04-18 17:06:51.332254] W [xlator.c:192:xlator_dynload] 0-xlator: /usr/local/lib/glusterfs/3.8dev/xlator/features/changetimerecorder.so: cannot open shared object file: No such file or directory
[2015-04-18 17:06:51.332289] E [graph.y:212:volume_type] 0-parser: Volume 'testvol-changetimerecorder', line 16: type 'features/changetimerecorder' is not valid or not found on this machine
[2015-04-18 17:06:51.332341] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume testvol-changetimerecorder
[2015-04-18 17:06:51.332514] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-04-18 17:06:51.332830] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down
[2015-04-18 17:08:55.145988] I [MSGID: 100030] [glusterfsd.c:2288:main] 0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/glusterfsd version 3.8dev (args: /usr/local/sbin/glusterfsd -s 10.70.43.164 --volfile-id testvol.10.70.43.164.tmp-brick1 -p /var/lib/glusterd/vols/testvol/run/10.70.43.164-tmp-brick1.pid -S /var/run/gluster/818424f21d804f3f9c42a0fe0e6c02ed.socket --brick-name /tmp/brick1 -l /var/log/glusterfs/bricks/tmp-brick1.log --xlator-option *-posix.glusterd-uuid=3ae0f8b2-ae34-4a7d-b8ea-3afd27e1356c --brick-port 49153 --xlator-option testvol-server.listen-port=49153)
[2015-04-18 17:08:55.162875] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2015-04-18 17:08:55.165398] W [xlator.c:192:xlator_dynload] 0-xlator: /usr/local/lib/glusterfs/3.8dev/xlator/features/changetimerecorder.so: cannot open shared object file: No such file or directory
[2015-04-18 17:08:55.165455] E [graph.y:212:volume_type] 0-parser: Volume 'testvol-changetimerecorder', line 16: type 'features/changetimerecorder' is not valid or not found on this machine 
[2015-04-18 17:08:55.165530] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume testvol-changetimerecorder
[2015-04-18 17:08:55.165714] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-04-18 17:08:55.166122] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down



Expected results:
Configured gluster with --disable-tiering. Shouldn't have seen these errors.


Additional info:

--- Additional comment from Anand Avati on 2015-04-19 09:44:06 CEST ---

REVIEW: http://review.gluster.org/10296 (tiering: skip CTR-xlator and config options when disabled) posted (#1) for review on master by Niels de Vos (ndevos)

--- Additional comment from Anand Avati on 2015-04-26 09:11:40 CEST ---

COMMIT: http://review.gluster.org/10296 committed in master by Vijay Bellur (vbellur) 
------
commit a675ab96b917fc48fc3d7ca035590ebd7cf102bd
Author: Niels de Vos <ndevos>
Date:   Sun Apr 19 09:40:34 2015 +0200

    tiering: skip CTR-xlator and config options when disabled
    
    When compiling with --disable-tiering, GlusterD should not contain any
    references to the ChangeTimeRecorder xlator or any of the data tiering
    options.
    
    BUG: 1213125
    Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/10296
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Gluster Build System <jenkins.com>

Comment 1 Anand Avati 2015-04-26 08:14:19 UTC
REVIEW: http://review.gluster.org/10378 (tiering: skip CTR-xlator and config options when disabled) posted (#1) for review on release-3.7 by Niels de Vos (ndevos)

Comment 2 Anand Avati 2015-04-26 14:35:37 UTC
COMMIT: http://review.gluster.org/10378 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 11ecab80a0ceb5fecf2dc04c0f9806b547c51c25
Author: Niels de Vos <ndevos>
Date:   Sun Apr 26 10:13:21 2015 +0200

    tiering: skip CTR-xlator and config options when disabled
    
    When compiling with --disable-tiering, GlusterD should not contain any
    references to the ChangeTimeRecorder xlator or any of the data tiering
    options.
    
    Cherry picked from commit a675ab96b917fc48fc3d7ca035590ebd7cf102bd:
    > BUG: 1213125
    > Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
    > Signed-off-by: Niels de Vos <ndevos>
    > Reviewed-on: http://review.gluster.org/10296
    > Reviewed-by: Dan Lambright <dlambrig>
    > Tested-by: Gluster Build System <jenkins.com>
    
    BUG: 1215382
    Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/10378
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 3 Niels de Vos 2015-05-14 17:27:25 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:28:46 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:20 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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