Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 17 Apr 2014 15:00:27 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12709062.1397745916632.132642.1397746827840@arcas>
In-Reply-To: <JIRA.12709062.1397745916632@arcas>
References: <JIRA.12709062.1397745916632@arcas>
Subject: [jira] [Commented] (ACCUMULO-2689) Replace ZK Process with in
 memory ZK for AccumuloMiniCluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973000#comment-13973000 ] 

Josh Elser commented on ACCUMULO-2689:
--------------------------------------

Is it a good idea to be working around what appear to be bad system configuration issues? You already stated on ACCUMULO-2554 that you think it plausible to be this.

Are there other benefits to starting ZK in process? Are you considering this a first step to making an in-process MAC?

> Replace ZK Process with in memory ZK for AccumuloMiniCluster
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-2689
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2689
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: mini
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>              Labels: zookeeper
>
> ACCUMULO-2554 describes zookeeper issues for various tests that use the MiniAccumuloCluster. One way to mitigate these might be to replace the zk process that we spin up with an in-memory zk that we can use. This would also potentially give us better logging into what is going on.


--
This message was sent by Atlassian JIRA
(v6.2#6252)