accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3306) Consider removing port-guess portion of PortUtils.getRandomFreePort
Date Tue, 25 Nov 2014 05:04:12 GMT


Josh Elser commented on ACCUMULO-3306:

Reading up on [TIME_WAIT|]...

On my desktop where I was seeing issues with this, {{net.ipv4.netfilter.ip_conntrack_tcp_timeout_time_wait}}
was, I believe, keeping sockets in TIME_WAIT for 60s before closing it fully. Reducing this
to a short amount (1s), addressed the issues that I was having.

{{echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait}}

Of course, this does come with consequences, so use with care.

> Consider removing port-guess portion of PortUtils.getRandomFreePort
> -------------------------------------------------------------------
>                 Key: ACCUMULO-3306
>                 URL:
>             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

View raw message