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

Yiqun Lin commented on HDFS-13346:
----------------------------------

Thanks [~elgoiri] for sharing the comments.
{quote}
You would have the same issue if A sets it to 200 and B later sets it to 300.
You have two admins doing conflicting operations.
{quote}
Agreed. Actually these should be the conflicting operations. Even though one 
admin set quota successfully, but after this the other admin do the new 
updating. The previous admin will see the false quota value. So I mean 
following way should be still okay:
{code}
One better way is that we invoke update operation this.rpcServer.setQuota in 
RouterAdminServer, not in RouterQuotaUpdateService.
{code}
[~liuhongtong], I think you can go ahead by this way, :).

> RBF: Fix synchronization of router quota and ns quota
> -----------------------------------------------------
>
>                 Key: HDFS-13346
>                 URL: https://issues.apache.org/jira/browse/HDFS-13346
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: liuhongtong
>            Assignee: liuhongtong
>            Priority: Major
>         Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> Source                    Destinations              Owner                     
> Group                     Mode                      Quota/Usage              
> /ns10t                    ns10->/ns10t              hadp                      
> hadp                      rwxr-xr-x                 [NsQuota: 150/319, 
> SsQuota: -/-]
> /ns10t/ns1mountpoint      ns1->/a/tt                hadp                      
> hadp                      rwxr-xr-x                 [NsQuota: -/-, SsQuota: 
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
>          150            -155            none             inf            3     
>      302                  0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> Source                    Destinations              Owner                     
> Group                     Mode                      Quota/Usage              
> /ns10t                    ns10->/ns10t              hadp                      
> hadp                      rwxr-xr-x                 [NsQuota: 400/319, 
> SsQuota: -/-]
> /ns10t/ns1mountpoint      ns1->/a/tt                hadp                      
> hadp                      rwxr-xr-x                 [NsQuota: -/-, SsQuota: 
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
>          150            -155            none             inf            3     
>      302                  0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to