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

Wei-Chiu Chuang commented on HDFS-13843:
----------------------------------------

I don't think [~zvenczel] would mind. [~ayushtkn] please help Zsolt to get this 
in!

> RBF: When we add/update mount entry to multiple destinations, unable to see 
> the order information in mount entry points and in federation router UI
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-13843
>                 URL: https://issues.apache.org/jira/browse/HDFS-13843
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: federation
>            Reporter: Soumyapn
>            Assignee: Ayush Saxena
>            Priority: Major
>              Labels: RBF
>         Attachments: HDFS-13843.01.patch, HDFS-13843.02.patch
>
>
> *Scenario:*
> Execute the below add/update command for single mount entry for single 
> nameservice pointing to multiple destinations. 
>  # hdfs dfsrouteradmin -add /apps1 hacluster /tmp1
>  # hdfs dfsrouteradmin -add /apps1 hacluster /tmp1,/tmp2,/tmp3
>  # hdfs dfsrouteradmin -update /apps1 hacluster /tmp1,/tmp2,/tmp3 -order 
> RANDOM
> *Actual*. With the above commands, mount entry is successfully updated.
> But order information like HASH, RANDOM is not displayed in mount entries and 
> also not displayed in federation router UI. However order information is 
> updated properly when there are multiple nameservices. This issue is with 
> single nameservice having multiple destinations.
> *Expected:* 
> *Order information should be updated in mount entries so that the user will 
> come to know which order has been set.*
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

Reply via email to