[
https://issues.apache.org/jira/browse/HDFS-16762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602090#comment-17602090
]
ASF GitHub Bot commented on HDFS-16762:
---------------------------------------
smarthanwang commented on PR #4867:
URL: https://github.com/apache/hadoop/pull/4867#issuecomment-1241454517
@ayushtkn thanks for comment. Changing the value of this conf really can
solve the problem, but it's not a good way. Because it need to review code and
find out this conf, it would wastes some time, and It also means that some
faults may have happpend.
I think making the default as true means that the routers prefer to
availabilty rather than consistence. It seems to be the opposite of hdfs.
> Make the default value of dfs.federation.router.client.allow-partial-listing
> as false.
> --------------------------------------------------------------------------------------
>
> Key: HDFS-16762
> URL: https://issues.apache.org/jira/browse/HDFS-16762
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: rbf
> Reporter: Chengwei Wang
> Assignee: Chengwei Wang
> Priority: Major
> Labels: pull-request-available
>
> AS the default value of
> _*dfs.federation.router.client.allow-partial-listing*_ is {*}_true_{*}, the
> hdfs client will got _*partial result*_ when one or more of the subclusters
> are unavailable for no permissions or other Exceptions, but _*user may not
> know.*_ It will lead to some fault.
> So I think it's better to make the default value as false.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
