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/08/01 17:40:41 UTC
[jira] [Created] (ACCUMULO-3036) 1.5 MiniCluster fails to start,
forces clients to wait indefinitely
Josh Elser created ACCUMULO-3036:
------------------------------------
Summary: 1.5 MiniCluster fails to start, forces clients to wait indefinitely
Key: ACCUMULO-3036
URL: https://issues.apache.org/jira/browse/ACCUMULO-3036
Project: Accumulo
Issue Type: Improvement
Components: mini
Affects Versions: 1.5.1, 1.5.0
Reporter: Josh Elser
Assignee: Josh Elser
Priority: Blocker
Fix For: 1.5.2
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
(v6.2#6252)