You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/12/08 03:11:12 UTC

[jira] [Updated] (ACCUMULO-3306) Consider removing port-guess portion of PortUtils.getRandomFreePort

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

Josh Elser updated ACCUMULO-3306:
---------------------------------
    Fix Version/s:     (was: 1.6.2)

> 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.7.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)