[
https://issues.apache.org/jira/browse/HDFS-13843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884671#comment-16884671
]
Ayush Saxena commented on HDFS-13843:
-------------------------------------
bq. hdfs dfsrouteradmin -update /apps1 hacluster /tmp1,/tmp2,/tmp3 -order RANDOM
This issue I guess started as some invalid scenario, the last update then would
overwrite the destination, and there would be only one destination. That in
/apps1 pointing to hacluster /tmp1,/tmp2,/tmp3 (you can't give destination as
comma separated values, that would be treated as 1 only).
Regarding the compatibility issues, for changing CLI, we may add a optional
parameter -d/ -details or -a/-all or something like that which can give all the
details not just order, but the readonly, fault tolerance and all. So this way
we can prevent incompatibility.
This how it was done for ls command for Ec, an optional extra parameter -e was
added
> 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: Zsolt Venczel
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
