accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1947) dfs.datanode.synconclose check is lacking
Date Mon, 02 Dec 2013 22:34:35 GMT

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

ASF subversion and git services commented on ACCUMULO-1947:
-----------------------------------------------------------

Commit c7fc776562275e417b0497ba47a2a5a212eca04f in branch refs/heads/1.5.1-SNAPSHOT from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=c7fc776 ]

ACCUMULO-1947 Remove forcefully setting the logger in a test with no reset after the test
is done.


> dfs.datanode.synconclose check is lacking
> -----------------------------------------
>
>                 Key: ACCUMULO-1947
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1947
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.5.1, 1.6.0
>
>
> The dfs configuration checks we now perform to support hdfs WALs includes a check for
dfs.datanode.synconclose which informs the datanode to flush to disk when a file is closed
instead of lazily writing the block (very important in the case of power failure).
> Looking at the actual check, it performs reflection on a CreateFlag class. In Apache
Hadoop 1.2.1, this class doesn't exist yet the option for dfs.datanode.synconclose does exist.
We should likely just reflect on the constant DFSConfigKeys.DFS_DATANODE_SYNCONCLOSE_KEY or
DFSConfigKeys.DFS_DATANODE_SYNCONCLOSE_DEFAULT to determine if that option is present.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message