[
https://issues.apache.org/jira/browse/HDFS-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614214#comment-15614214
]
Lantao Jin commented on HDFS-11060:
-----------------------------------
Paginated on NN UI sounds good. And please knows that we need an interface to
get all corrupted/missing blocks by http/https request as easy as possible. For
example, no paginated result from "https://nn:50070/fsck?"; is better for using.
> 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: [email protected]
For additional commands, e-mail: [email protected]
