[
https://issues.apache.org/jira/browse/ACCUMULO-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846912#comment-13846912
]
ASF subversion and git services commented on ACCUMULO-1999:
-----------------------------------------------------------
Commit 622fc7d20744ae8a7e75ba0dc945777f94254b48 in branch
refs/heads/1.6.0-SNAPSHOT from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=622fc7d ]
ACCUMULO-1999 Backport changes from 1664 which advertise the Master's random
port
> Random port for Master doesn't make sense
> -----------------------------------------
>
> Key: ACCUMULO-1999
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1999
> Project: Accumulo
> Issue Type: Bug
> Components: master
> Affects Versions: 1.5.0
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.5.1
>
> Attachments:
> 0001-ACCUMULO-1999-Backport-changes-from-1664-which-adver-3.patch,
> 0001-ACCUMULO-1999-Backport-changes-from-1664-which-adver.patch
>
>
> I was looking at ACCUMULO-1664. In 1.5.0, it appears that you can configure a
> port of 0 for the master. The master will bind itself to a random port, but
> none of the other procs know what that port was, so you just shot yourself in
> the foot.
> I'd like to bring those changes back to 1.5.1 so a port of 0 actually works
> with the master and doesn't leave you with a broken system.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
