accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-1999) Random port for Master doesn't make sense
Date Tue, 10 Dec 2013 21:48:09 GMT


Josh Elser updated ACCUMULO-1999:

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

Backport of ACCUMULO-1664 if anyone wants to review. I tested the following:

# Random monitor, log4j, master, tserver procs and updates to other procs when those are restarted
# Log4j forwarding works after restart
# ZooKeeper lock advertisement for master is updated after new master is start
# `accumulo info` is updated after new master is started.

> Random port for Master doesn't make sense
> -----------------------------------------
>                 Key: ACCUMULO-1999
>                 URL:
>             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.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

View raw message