[
https://issues.apache.org/jira/browse/HDFS-14193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738649#comment-16738649
]
Ayush Saxena commented on HDFS-14193:
-------------------------------------
[~elgoiri] By far management is considered the only legitimate way that I got
is that If no value is configured.That means admin didn't want to have a
default namespace.If that is not configured we shouldn't use it too.So by
solution if the defaultNS isn't configured we can set the parameter to false
and don't set any NS to default.
If we move to other side like we need to give a default NS even if it is not
configured.I don't see any algorithm that doesn't have a loop on its side or
sounds completely logical.
I have shooted v1 with the first alt.
Up for discussion :)
> RBF: Inconsistency with the Default Namespace
> ---------------------------------------------
>
> Key: HDFS-14193
> URL: https://issues.apache.org/jira/browse/HDFS-14193
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: HDFS-14193-HDFS-13891-01.patch
>
>
> In the present scenario, if the default nameservice is not explicitly
> mentioned.Each router fallbacks to it local namespace as Default.There in
> each router having different default namespaces. Which leads to
> inconsistencies in operations and even blocks in maintaining a global uniform
> state. The outputs becomes specific to which router is serving the request
> and is different with different routers.
--
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
