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] [Resolved] (ACCUMULO-3233) Random port for ZK in MiniAccumulo might not be unique
Date Wed, 15 Oct 2014 01:07:34 GMT

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

Josh Elser resolved ACCUMULO-3233.
----------------------------------
    Resolution: Fixed

Fixed this downstream instead of in MAC itself (as the fix is much easier to manage). We can
try to identify the circumstances in which we ran into the issue and then retry in the IT
test harness.

As such, 1.5.3 was dropped from the fixVersion as it doesn't have these classes.

> Random port for ZK in MiniAccumulo might not be unique
> ------------------------------------------------------
>
>                 Key: ACCUMULO-3233
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3233
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: mini
>    Affects Versions: 1.5.2, 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> To start ZooKeeper in a way that won't interfere with other processes on the node, we
have to choose a "random" port on the node and then configure Accumulo with that port (as
we don't have a means to get the random port that ZooKeeper itself would bind to).
> The problem is that there is a delay between our choosing of a random port and ZooKeeper
binding to that port which introduces a race condition.



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

Mime
View raw message