New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDFS-16762. Make the default value of dfs.federation.router.client.allow-partial-listing as false. #4867
base: trunk
Are you sure you want to change the base?
Conversation
…low-partial-listing as false.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing defaults is an incompatible change and this behaviour is there since very starting. I don't think we need to change this
💔 -1 overall
This message was automatically generated. |
@ayushtkn we had a discussion about this in a previous JIRA. @smarthanwang unfortunately, we cannot do this change according to the defaults policies. |
@goiri @ayushtkn thanks for comment. |
the behaviour is configurable, we can't change the default, but if you want this behaviour you can explicitly change the value of this conf in your prod cluster and get things sorted. |
@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. |
Description of PR
https://issues.apache.org/jira/browse/HDFS-16762
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.