hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "panlijie (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-13476) HDFS (Hadoop/HDP reports CORRUPT files
Date Mon, 08 Jul 2019 11:59:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880250#comment-16880250

panlijie edited comment on HDFS-13476 at 7/8/19 11:58 AM:

{{ [~brahmareddy] HDP is not the hadoop2.7.3,it`s newer then hadoop2.7.3
and has maney changes by hortonworks developer}}

was (Author: panlijie):
h1.  [~brahmareddy] HDP is not the hadoop2.7.3,it`s newer then hadoop2.7.3
and has maney changes by hortonworks developer

> HDFS (Hadoop/HDP reports CORRUPT files
> --------------------------------------------------------
>                 Key: HDFS-13476
>                 URL: https://issues.apache.org/jira/browse/HDFS-13476
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.7.4
>            Reporter: feng xu
>            Priority: Critical
> We have a security software runs on local file system(ext4), and the security software
denies some particular users to access some {color:#333333}particular {color}HDFS folders
based on security policy. For example, the security policy always gives the user hdfs full
permission, and denies the user yarn to access /dir1.  If the user yarn tries to access a
file under HDFS folder {color:#333333}/dir1{color}, the security software denies the access
and returns EACCES from file system call through errno. This used to work because the data
corruption was determined by block scanner([https://blog.cloudera.com/blog/2016/12/hdfs-datanode-scanners-and-disk-checker-explained/).]
> On HDP, HDFS reports a lot data corruptions because of the security
policy to deny file access in HDFS from local file system. We debugged HDFS and found out BlockSender()
directly calls the following statements and may cause the problem:
> datanode.notifyNamenodeDeletedBlock(block, replica.getStorageUuid());
>  datanode.data.invalidate(block.getBlockPoolId(), new Block[]\{block.getLocalBlock()});
> In the mean time, the block scanner is not triggered because of the undocumented property
{color:#333333}dfs.datanode.disk.check.min.gap. However the problem is still there if we disable dfs.datanode.disk.check.min.gap{color}
by setting it to 0. . 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message