[Bugs] [Bug 1452006] New: tierd listens to a port.
bugzilla at redhat.com
bugzilla at redhat.com
Thu May 18 07:06:22 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1452006
Bug ID: 1452006
Summary: tierd listens to a port.
Product: GlusterFS
Version: mainline
Component: tiering
Severity: low
Assignee: bugs at gluster.org
Reporter: hgowtham at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
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:
--
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