[
https://issues.apache.org/jira/browse/HDFS-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966538#comment-16966538
]
Ayush Saxena commented on HDFS-14815:
-------------------------------------
Thanx [~LiJinglun] for the patch. I too prefer the first approach. Seems Like
ViewFs Also rejects operations on mount with something like InternalMountPoint
is Read only type. I don't recall Exactly.
But I think we should rather be throwing Back an ACE to the client, telling
him, that he doesn't have the permission, rather than an IOE, telling it is
communicating with router and it is a mount entry.
IMO Ideally, we shouldn't expose to the client whether he is directly
communicating with Router or NN in a normal Client Operation.
> RBF: Update the quota in MountTable when calling setQuota on a MountTable src.
> ------------------------------------------------------------------------------
>
> Key: HDFS-14815
> URL: https://issues.apache.org/jira/browse/HDFS-14815
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Attachments: HDFS-14815.001.patch
>
>
> The method setQuota() can make the remote quota(the quota on real clusters)
> inconsistent with the MountTable. I think we have 3 ways to fix it:
> # Reject all the setQuota() rpcs if it trys to change the quota of a mount
> table.
> # Let setQuota() to change the mount table quota. Update the quota on zk
> first and then update remote quotas.
> # Do nothing. The RouterQuotaUpdateService will finally make all the remote
> quota right. We can tolerate short-term inconsistencies.
> I'd like option 1 because I want the RouterAdmin to be the only entrance to
> update the MountTable.
> Option 3 we don't need change anything, but the quota will be inconsistent
> for a short-term. The remote quota will be effective immediately and
> auto-changed back after a while. User might be confused about the behavior.
> Â
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
