[
https://issues.apache.org/jira/browse/HDFS-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinglun updated HDFS-14815:
---------------------------
Description:
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.
was:
When we call setQuota on a MountTable, may be we can update the quota of the
MountTable too. So the quota of the MountTable won't be inconsistent with the
quota of the remote locations.
Each time Router does setQuota() on a MountTable, it changes the quota in the
MountTable and let RouterQuotaUpdateService finally make all the quota right.
(After HDFS-14814 RouterQuotaUpdateService will make all the quota consistent
with MountTable)
> 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
>
> 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]
