accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-3036) 1.5 MiniCluster fails to start, forces clients to wait indefinitely
Date Thu, 21 May 2015 23:12:17 GMT


Christopher Tubbs resolved ACCUMULO-3036.
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.5.3)

This issue was marked to be fixed for 1.5.3. However, no patch has been provided, and development
on 1.5 is waning. Non-urgent issues are not likely to be addressed. Users are encouraged to
upgrade to a newer version of Accumulo.

> 1.5 MiniCluster fails to start, forces clients to wait indefinitely
> -------------------------------------------------------------------
>                 Key: ACCUMULO-3036
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: mini
>    Affects Versions: 1.5.0, 1.5.1
>            Reporter: Josh Elser
> Over in Pig land, a user was complaining about a test which used MiniAccumuloCluster
that hung until the JUnit timeout was hit.
> Eventually, the problem was diagnosed as a bad classpath (old version of Thrift was included
and used), which was causing the TServer and Master to immediately bail out. However, the
client sat indefinitely trying to connect unsuccessfully.
> MAC#start should not return before we're sure that the processes are actually up and
running (a very quick smoke test).
> It looks like ACCUMULO-1537 introduced a call to SetGoalState on the Master before MAC#start
returned which would (I assume) fail and then throw a RTE if the Master decided to die. Including
this fix in 1.5 may be sufficient to fix the underlying issue the user was seeing.

This message was sent by Atlassian JIRA

View raw message