You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Lantao Jin (JIRA)" <ji...@apache.org> on 2016/11/02 14:02:58 UTC

[jira] Lantao Jin shared "HDFS-11060: make DEFAULT_MAX_CORRUPT_FILEBLOCKS_RETURNED configurable" with you

    Lantao Jin shared an issue with you
    -----------------------------------

    

> make DEFAULT_MAX_CORRUPT_FILEBLOCKS_RETURNED configurable
> ---------------------------------------------------------
>
>                 Key: HDFS-11060
>                 URL: https://issues.apache.org/jira/browse/HDFS-11060
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>            Reporter: Lantao Jin
>            Priority: Minor
>
> Current, the easiest way to determine which blocks is missing is using NN web UI or JMX. Unfortunately, because the DEFAULT_MAX_CORRUPT_FILEBLOCKS_RETURNED=100 is hard code in FSNamesystem, only 100 missing blocks can be return by UI and JMX. Even the result of URL "https://nn:50070/fsck?listcorruptfileblocks=1&path=%2F" is limited by this hard code value too.
> I did know FSCK can return more than 100 result but due to the security reason(with kerberos), it is very hard to involve to costumer programs and scripts.
> So I think it should add a configurable var "maxCorruptFileBlocksReturned" to fix above case.
> If community also think it's worth to do, I will patch this. If not, please feel free to tell me the reason. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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