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

Zsolt Venczel commented on HDFS-13843:
--------------------------------------

Thanks for your feedback [~SoumyaPN]!
{quote}Sure.It doesn't . It was related to showing up the info in UI when two 
destinations are mounted to one NS.NS1->tmp1 and NS1->tmp2 then in the UI it 
was not showing order.
{quote}
I might have misunderstood but based on the description _"But order information 
like HASH, RANDOM is not displayed in mount entries and also not displayed in 
federation router UI."_ the order information was not displayed in mount 
entries *and* not displayed in the UI.
 I added the order information that was missing and fixed the UI as it was not 
displaying order information ever (not just in case of multiple destinations).
Based on your reply I assume the UI fix is needed only. Am I right?

{quote}There is already one JIRA addressing it.
{quote}
Can you point me to that jira? Should this jira be closed as a duplicate then?

You are right about compatibility problems. Would adding a new command to 
require the Order list be more beneficial?

Best regards,
 Zsolt

> 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.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