accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3306) Consider removing port-guess portion of PortUtils.getRandomFreePort
Date Thu, 06 Nov 2014 17:10:34 GMT

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

Josh Elser updated ACCUMULO-3306:
---------------------------------
    Issue Type: Improvement  (was: Bug)

> Consider removing port-guess portion of PortUtils.getRandomFreePort
> -------------------------------------------------------------------
>
>                 Key: ACCUMULO-3306
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3306
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>
> I recently changed how SimpleMacIT and ConfigurableMacIT start the mini cluster in an
attempt to mitigate ZooKeeper failing to start when the port we guessed at was already in
use. In last night's run of integration tests on master, we had 22 occurrences of the warning
("Failed to start MiniAccumuloCluster, assumably due to ZooKeeper issues").
> I'm wondering if we can do anything to getRandomFreePort to make it more reliable. Would
not providing a port (0) and letting it find one for itself be more stable?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message