You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Soumyapn (JIRA)" <ji...@apache.org> on 2018/09/14 11:38:00 UTC

[jira] [Created] (HDFS-13917) RBF: Successfully updated mount point message is coming if we update the mount entry by passing the nameservice id for which mount entry is not present

Soumyapn created HDFS-13917:
-------------------------------

             Summary: RBF: Successfully updated mount point message is coming if we update the mount entry by passing the nameservice id for which mount entry is not present
                 Key: HDFS-13917
                 URL: https://issues.apache.org/jira/browse/HDFS-13917
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Soumyapn


*Test Steps:*
 # Add the mount entry like "hdfs dfsrouteradmin -add /apps *{color:#14892c}hacluster{color}* /opt
 # Update the mount entry by giving {color:#14892c}*hacluster2 "*{color:#333333}hdfs dfsrouteradmin -update /apps *{color:#14892c}hacluster2{color}* /opt -readonly.{color}{color}

*{color:#14892c}{color:#333333}Actual Result:{color}{color}*

{color:#14892c}{color:#333333}Console message says "Successfully updated mount entry for /apps"{color}{color}

*{color:#14892c}{color:#333333}Expected Result:{color}{color}*

{color:#14892c}{color:#333333}This console message will be confusing and the user will be in a impression that the mount entry is readonly updated. But we have passed the nameservice for which the mount entry is not present.{color}{color}

{color:#14892c}{color:#333333}Console message can be like *"There is no entries for the hacluster2 nameservice"* so that the user will have proper message on the update command executed.{color}{color}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org