Bug 1716766 - [Thin-arbiter] TA process is not picking 24007 as port while starting up
Summary: [Thin-arbiter] TA process is not picking 24007 as port while starting up
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ashish Pandey
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-04 05:18 UTC by Ashish Pandey
Modified: 2019-06-08 05:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-08 05:40:05 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Gluster.org Gerrit 22811 None Merged cluster/replicate: Modify command in unit file to assign port correctly 2019-06-08 05:40:04 UTC

Description Ashish Pandey 2019-06-04 05:18:20 UTC
Description of problem:
TA process is not picking 24007 as port while starting up.


Problem:

In unit file of TA process we have been using ta-vol as volume id and also 
 ta-vol-server.transport.socket.listen-port=24007

In our volume file for TA process we only consider volname as "ta" and not as "ta-vol".
That's why it was not able to assign this port number to or ta process as in volume file it will try to find server xlato as ta-vol

volume ta-server  <<<<<<<<< not ta-vol
 46     type protocol/server
 47     option transport.listen-backlog 10
 48     option transport.socket.keepalive-count 9
 49     option transport.socket.keepalive-interval 2
 50     option transport.socket.keepalive-time 20
 51     option transport.tcp-user-timeout 0
 52     option transport.socket.keepalive 1
 53     option auth.addr./mnt/thin-arbiter.allow *
 54     option auth-path /mnt/thin-arbiter
 55     option transport.address-family inet
 56     option transport-type tcp
 57     subvolumes ta-io-stats
 58 end-volume      




Solution:
Just need to change the command which Unit file is going to execute.

Comment 1 Worker Ant 2019-06-04 06:01:29 UTC
REVIEW: https://review.gluster.org/22811 (cluster/replicate: Modify command in unit file to assign port correctly) posted (#1) for review on master by Ashish Pandey

Comment 2 Worker Ant 2019-06-08 05:40:05 UTC
REVIEW: https://review.gluster.org/22811 (cluster/replicate: Modify command in unit file to assign port correctly) merged (#4) on master by Amar Tumballi


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