accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1664) Make all processes able to use random ports
Date Tue, 27 Aug 2013 14:31:52 GMT


Billie Rinaldi commented on ACCUMULO-1664:

When the master obtains the lock, the port hasn't been assigned yet.  Currently if you set
the port to 0, it will say 0 in zookeeper yet the process will be listening on a random port.

The TNonblockingServerSocket class is a simple wrapper for ServerSocketChannel.  In the patch
I'm experimenting with, I just copied that class and added a getPort method.  I'm not sure
how important it is to have the master lock obtained when it is.  I was worried about moving
it, so I added another zookeeper node under /master for the real address.  Definitely looking
for feedback on this and some other aspects of the patch.
> Make all processes able to use random ports
> -------------------------------------------
>                 Key: ACCUMULO-1664
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor, proxy
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
> One method of assigning random ports (currently used by the MiniAccumuloCluster) involves
finding open ports and configuring Accumulo with them.  However, the selected ports could
become occupied before the Accumulo processes are able to claim them.
> All the processes can be assigned random ports by setting the desired port to 0, but
not all of them are then discoverable.  In particular, the master, monitor and proxy would
need to be addressed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message