accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3865) miniDFS not reinitialized on MiniAccumuloClusterImpl
Date Tue, 09 Jun 2015 16:28:00 GMT


Josh Elser commented on ACCUMULO-3865:

bq. Am I correct in stating that this is not currently a problem in any of our tests

Right, I think we just haven't stumbled onto it.

bq. but that it does constrain what kinds of tests we (and other consumers of MiniAccumuloCluster)
can write?

Yea, enough monkeys behind keyboards writing tests, and we likely would've stumbled onto it.

bq. If that's the case, we could probably offer a more explicit error (new IllegalStateException("Cannot
re-start mini when using mini DFS")) for now.

+1 That would be a good improvement over what we currently have. Some javadoc on the {{useMiniDFS()}}
method (or whatever it is) would also be good IMO.

> miniDFS not reinitialized on MiniAccumuloClusterImpl
> ----------------------------------------------------
>                 Key: ACCUMULO-3865
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: mini
>    Affects Versions: 1.6.0, 1.6.1, 1.6.2
>            Reporter: Josh Elser
>             Fix For: 1.6.3, 1.7.1, 1.8.0
> Noticed this looking at ACCUMULO-3864.
> {{stop()}} nulls the miniDFS local member, but it's only initialized in the constructor,
not {{start()}}.
> Calling {{start()}} after a {{stop()}} when {{useMiniDFS(true)}} will hang indefinitely
because the filesystem is unavailable. It will likely also NPE in certain places.

This message was sent by Atlassian JIRA

View raw message