accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Berman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1631) MiniAccumuloCluster's MiniDFS data directory is created relative to the working directory
Date Thu, 01 Aug 2013 20:23:48 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Berman updated ACCUMULO-1631:
-------------------------------------

    Status: Patch Available  (was: Open)

Unfortunately it seems like the only way to fix this is to use System.setProperty() to override
the MiniDFS defaults (it looks from the code initially like it can be overridden with a combination
of constructor flags and config switches, but the same property is referenced deeper in the
code without respect to those switches).

Also had to change the expected permissions from 775 to 755, since MiniDFS creates the directories
under there with no particular permissions, making them 755, but then immediately tries to
verify that they have the permissions you requested, which fails if you requested anything
else.

This fixes many integration test failures of the form "Cannot lock storage build/test/data/dfs/name1.
The directory is already locked" on my local build
                
> MiniAccumuloCluster's MiniDFS data directory is created relative to the working directory
> -----------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1631
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1631
>             Project: Accumulo
>          Issue Type: Bug
>          Components: mini
>    Affects Versions: 1.5.0
>            Reporter: Michael Berman
>            Assignee: Michael Berman
>         Attachments: ACCUMULO-1631.patch
>
>
> Seems like it should go in one of the directories passed in the MiniAccumuloConfig (where
other namenode and datanode data already go).
> This is causing integration tests to fail on my local machine, since every test tries
to use the same dfs tree but they're not always cleaned up and unlocked nicely over the lifespan
of the tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message