Bug 1452006 - tierd listens to a port.
Summary: tierd listens to a port.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: hari gowtham
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks: 1456682 1457289
TreeView+ depends on / blocked
 
Reported: 2017-05-18 07:06 UTC by hari gowtham
Modified: 2017-09-05 17:30 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.12.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1456682 (view as bug list)
Environment:
Last Closed: 2017-09-05 17:30:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description hari gowtham 2017-05-18 07:06:22 UTC
Description of problem:
the tier daemon listen to a port. which is not necessary

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

How reproducible:
100%

Steps to Reproduce:
1.create a volume.
2.attach a hot tier and make it a tiered volume.
3.gluster v status

Actual results:
 gluster v status
Status of volume: v1
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick 192.168.122.17:/data/gluster/bricks/h
b2                                          49155     0          Y       3282 
Brick 192.168.122.17:/data/gluster/bricks/h
b1                                          49154     0          Y       3263 
Cold Bricks:
Brick 192.168.122.17:/data/gluster/bricks/b
1                                           49152     0          Y       3192 
Brick 192.168.122.17:/data/gluster/bricks/b
2                                           49153     0          Y       3211 
Tier Daemon on localhost                    49156     0          Y       3306 
 
Task Status of Volume v1
------------------------------------------------------------------------------
There are no active volume tasks

tier has a TCP port value.

Expected results:
 gluster v status              
Status of volume: v1
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick 192.168.122.17:/data/gluster/bricks/h
b2                                          49155     0          Y       26795
Brick 192.168.122.17:/data/gluster/bricks/h
b1                                          49154     0          Y       26776
Cold Bricks:
Brick 192.168.122.17:/data/gluster/bricks/b
1                                           49152     0          Y       26705
Brick 192.168.122.17:/data/gluster/bricks/b
2                                           49153     0          Y       26724
Tier Daemon on localhost                    N/A       N/A        Y       26941
 
Task Status of Volume v1
------------------------------------------------------------------------------
There are no active volume tasks

The TCP port and RDMA have to be N/A

Additional info:

Comment 1 Worker Ant 2017-05-18 08:48:41 UTC
REVIEW: https://review.gluster.org/17328 (Tier: removing port allocated for tier) posted (#1) for review on master by hari gowtham (hari.gowtham005)

Comment 2 Worker Ant 2017-05-19 06:38:52 UTC
REVIEW: https://review.gluster.org/17328 (Tier: removing port allocated for tier) posted (#2) for review on master by hari gowtham (hari.gowtham005)

Comment 3 Worker Ant 2017-05-29 11:06:51 UTC
REVIEW: https://review.gluster.org/17328 (Tier: removing port allocated for tier) posted (#3) for review on master by hari gowtham (hari.gowtham005)

Comment 4 Worker Ant 2017-05-30 00:37:48 UTC
COMMIT: https://review.gluster.org/17328 committed in master by Shyamsundar Ranganathan (srangana) 
------
commit 0a8b2db2d2c3993b25272a65fecad0d3d2866607
Author: hari gowtham <hgowtham>
Date:   Thu May 18 14:15:39 2017 +0530

    Tier: removing port allocated for tier
    
    Problem: Tier has a port which it doesn't use.
    
    Fix: Remove the port getting allocated for tier.
    
    Change-Id: If0fe393fc335d9f622a063787e0a3c6db9b7a50c
    BUG: 1452006
    Signed-off-by: hari gowtham <hgowtham>
    Reviewed-on: https://review.gluster.org/17328
    Tested-by: hari gowtham <hari.gowtham005>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>

Comment 5 Worker Ant 2017-05-30 10:22:53 UTC
REVIEW: https://review.gluster.org/17419 (tier: port value missing on cli parsing) posted (#1) for review on master by hari gowtham (hari.gowtham005)

Comment 6 Worker Ant 2017-05-31 11:39:24 UTC
COMMIT: https://review.gluster.org/17419 committed in master by Atin Mukherjee (amukherj) 
------
commit 57b0a4a374a604079f37a9d9d9fffb09a718c010
Author: hari gowtham <hgowtham>
Date:   Tue May 30 15:50:25 2017 +0530

    tier: port value missing on cli parsing
    
    problem: as tier didn't have a port all the values regarding
    the port were removed. but the cli needs a port value to parse and
    print the status.
    
    fix: fake the port value with a zero.
    
    Change-Id: I6491f6c441f7cfddbdaa724fcbe7c30e348aa765
    BUG: 1452006
    Signed-off-by: hari gowtham <hgowtham>
    Reviewed-on: https://review.gluster.org/17419
    Smoke: Gluster Build System <jenkins.org>
    Tested-by: hari gowtham <hari.gowtham005>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Reviewed-by: Prashanth Pai <ppai>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Samikshan Bairagya <samikshan>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 7 Shyamsundar 2017-09-05 17:30:44 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.12.0, please open a new bug report.

glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/


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