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

Hudson commented on HDFS-13843:
-------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17220 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17220/])
HDFS-13843. RBF: Add optional parameter -d for detailed listing of mount 
(ayushsaxena: rev c3abfcefdd256650b2a45ae2aac53c4a22721a46)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-rbf/src/test/java/org/apache/hadoop/hdfs/server/federation/router/TestRouterAdminCLI.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSCommands.md
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/tools/federation/RouterAdmin.java


> RBF: Add optional parameter -d for detailed listing of mount points.
> --------------------------------------------------------------------
>
>                 Key: HDFS-13843
>                 URL: https://issues.apache.org/jira/browse/HDFS-13843
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: federation
>            Reporter: Soumyapn
>            Assignee: Ayush Saxena
>            Priority: Major
>              Labels: RBF
>             Fix For: 3.3.0
>
>         Attachments: HDFS-13843-03.patch, HDFS-13843-04.patch, 
> 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
(v8.3.2#803003)

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

Reply via email to