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] [Commented] (ACCUMULO-2985) MAC doesn't stop cleanly in 1.6.1-SNAPSHOT
Date Fri, 11 Jul 2014 15:34:05 GMT

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

Josh Elser commented on ACCUMULO-2985:
--------------------------------------

There's a single non-daemon thread. To implement ACCUMULO-2764, I wrapped the methods which
stop the MAC sub processes in {{Callable}}'s so we can get the timeout semantics. Sadly, this
requires an Executor to get those timeout semantics. That Executor wasn't being stopped which
introduced the bug that the above program outlines.

I'm guessing that because Maven ultimately just ends the forked process, we never noticed
that the surefire runner wasn't cleanly exiting on its own.

> MAC doesn't stop cleanly in 1.6.1-SNAPSHOT
> ------------------------------------------
>
>                 Key: ACCUMULO-2985
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2985
>             Project: Accumulo
>          Issue Type: Bug
>          Components: mini
>            Reporter: John Vines
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.6.1, 1.7.0
>
>
> Using the following code to do some work-
> {code}public class TestMACWithRealInstance {
>   public static void main(String args[]) throws IOException, AccumuloException, AccumuloSecurityException,
TableExistsException, InterruptedException {
>     MiniAccumuloConfig macConfig = new MiniAccumuloConfig(new File("/tmp/mac"), "secret");
>     macConfig.setNumTservers(2);
>     MiniAccumuloCluster mac = new MiniAccumuloCluster(macConfig);
>     mac.start();
>     mac.getConnector("root", "secret").tableOperations().create("macCreated");
>     mac.stop();
>   }
> }
> {code}
> It works fine against 1.6.0, but it seems broken against 01da4f4a8b14a125d3a2e29ef98dd044ab9ec75f
after calling stop() it just sits in the terminal spewing messages about unable to connect
to zookeeper



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

Mime
View raw message