[ 
https://issues.apache.org/jira/browse/HDFS-15510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179106#comment-17179106
 ] 

Íñigo Goiri commented on HDFS-15510:
------------------------------------

The situation is a little tricky...
It may make sense to go for something like #2 and evenly distribute the quota 
across the destinations.
So in your case, you set it to 10, we set 5 to one destination and 5 to the 
other.
If you have say 3 locations and set it to 20, one could set each to 7, 7 and 6.
It has the issue that some might get unbalanced but I think is the best we can 
do.
Then we could even rebalance the quotas with the quota service if needed.

[~linyiqun] any thoughts on this?

> RBF: Quota and Content Summary was not correct in Multiple Destinations
> -----------------------------------------------------------------------
>
>                 Key: HDFS-15510
>                 URL: https://issues.apache.org/jira/browse/HDFS-15510
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Hemanth Boyina
>            Assignee: Hemanth Boyina
>            Priority: Critical
>         Attachments: 15510.png
>
>
> steps :
> *) create a mount entry with multiple destinations ( for suppose 2)
> *) Set NS quota as 10 for mount entry by dfsrouteradmin command, Content 
> Summary on the Mount Entry shows NS quota as 20
> *) Create 10 files through router, on creating 11th file , NS Quota Exceeded 
> Exception is coming 
> though the Content Summary showing the NS quota as 20 , we are not able to 
> create 20 files
>  
> the problem here is router stores the mount entry's NS quota as 10 , but 
> invokes NS quota on both the name services by set NS quota as 10 , so content 
> summary on mount entry aggregates the content summary of both the name 
> services by making NS quota as 20



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to