Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 11 Dec 2013 01:42:10 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12683872.1386695273250.14270.1386726130911@arcas>
In-Reply-To: <JIRA.12683872.1386695273250@arcas>
References: <JIRA.12683872.1386695273250@arcas>
Subject: [jira] [Updated] (ACCUMULO-1999) Random port for Master doesn't
 make sense
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-1999:
---------------------------------

    Attachment: 0001-ACCUMULO-1999-Backport-changes-from-1664-which-adver-3.patch

Screwed up patch2. Patch 3 with the changes that 2 claimed to have.

> 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)