[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-06-24 Thread Hudson (JIRA)


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

Hudson commented on HDFS-14193:
---

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16813 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16813/])
HDFS-14193. RBF: Inconsistency with the Default Namespace. Contributed (brahma: 
rev c012b09fb678db11a10d0a8e1f64ee1a7229a417)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-rbf/src/test/java/org/apache/hadoop/hdfs/server/federation/resolver/TestInitializeMountTableResolver.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/resolver/MountTableResolver.java


> 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
> Fix For: HDFS-13891
>
> Attachments: HDFS-14193-HDFS-13891-01.patch, 
> HDFS-14193-HDFS-13891-02.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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-16 Thread Vinayakumar B (JIRA)


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

Vinayakumar B commented on HDFS-14193:
--

Committed to HDFS-13891.

Thanks [~ayushtkn] and [~elgoiri].

> 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
> Fix For: HDFS-13891
>
> Attachments: HDFS-14193-HDFS-13891-01.patch, 
> HDFS-14193-HDFS-13891-02.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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-10 Thread JIRA


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

Íñigo Goiri commented on HDFS-14193:


+1 on [^HDFS-14193-HDFS-13891-02.patch].

> 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, 
> HDFS-14193-HDFS-13891-02.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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread Ayush Saxena (JIRA)


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

Ayush Saxena commented on HDFS-14193:
-

The two tests are the ones which were the scenario of fallbacks when default NS 
was not specified.As of now we will not be having any fallback.So we can't get 
them in.There are now 3 scenarios possible now in the present and I think the 
test present covers those three. If you think need of any more scenarios other 
than being covered.Would get them in too. :)


> 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, 
> HDFS-14193-HDFS-13891-02.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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on HDFS-14193:
--

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
|| || || || {color:brown} HDFS-13891 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 19m 
56s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
28s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
19s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green}  0m 
32s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
13m 20s{color} | {color:green} branch has no errors when building and testing 
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
55s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
34s{color} | {color:green} HDFS-13891 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green}  0m 
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
13m 22s{color} | {color:green} patch has no errors when building and testing 
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  1m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
34s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 22m 
40s{color} | {color:green} hadoop-hdfs-rbf in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
26s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 77m 12s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | HDFS-14193 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12954359/HDFS-14193-HDFS-13891-02.patch
 |
| Optional Tests |  dupname  asflicense  compile  javac  javadoc  mvninstall  
mvnsite  unit  shadedclient  findbugs  checkstyle  |
| uname | Linux e9310a56e284 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 
08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | HDFS-13891 / 8c245e7 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_191 |
| findbugs | v3.1.0-RC1 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HDFS-Build/25944/testReport/ |
| Max. process+thread count | 1000 (vs. ulimit of 1) |
| modules | C: hadoop-hdfs-project/hadoop-hdfs-rbf U: 
hadoop-hdfs-project/hadoop-hdfs-rbf |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/25944/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> RBF: Inconsistency with the Default Namespace
> -
>
> 

[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread JIRA


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

Íñigo Goiri commented on HDFS-14193:


Should we leave some of the old unit tests with the assert fixed? Or do you 
think the one there now covers those 3 old ones?

> 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, 
> HDFS-14193-HDFS-13891-02.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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread Ayush Saxena (JIRA)


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

Ayush Saxena commented on HDFS-14193:
-

Thanks [~elgoiri]

Have put in a log when the default name service is disabled.

Pls Review

> 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, 
> HDFS-14193-HDFS-13891-02.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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on HDFS-14193:
--

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
|| || || || {color:brown} HDFS-13891 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m 
34s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
29s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
20s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green}  0m 
33s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
12m 47s{color} | {color:green} branch has no errors when building and testing 
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
52s{color} | {color:green} HDFS-13891 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
32s{color} | {color:green} HDFS-13891 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
28s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}  
0m 17s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs-rbf: The patch 
generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green}  0m 
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
13m 18s{color} | {color:green} patch has no errors when building and testing 
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
31s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 22m 
49s{color} | {color:green} hadoop-hdfs-rbf in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
24s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 77m  2s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | HDFS-14193 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12954351/HDFS-14193-HDFS-13891-01.patch
 |
| Optional Tests |  dupname  asflicense  compile  javac  javadoc  mvninstall  
mvnsite  unit  shadedclient  findbugs  checkstyle  |
| uname | Linux 1b7bd59e4551 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 
08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | HDFS-13891 / 8c245e7 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_191 |
| findbugs | v3.1.0-RC1 |
| checkstyle | 
https://builds.apache.org/job/PreCommit-HDFS-Build/25942/artifact/out/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HDFS-Build/25942/testReport/ |
| Max. process+thread count | 975 (vs. ulimit of 1) |
| modules | C: hadoop-hdfs-project/hadoop-hdfs-rbf U: 
hadoop-hdfs-project/hadoop-hdfs-rbf |
| Console output | 

[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread JIRA


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

Íñigo Goiri commented on HDFS-14193:


I guess this is fine, we may want to log the case where we don't do anything 
when the default is not enabled.
Similar to the log that is already there but updated to the new case.

> 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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread Ayush Saxena (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-14193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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



[jira] [Commented] (HDFS-14193) RBF: Inconsistency with the Default Namespace

2019-01-09 Thread JIRA


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

Íñigo Goiri commented on HDFS-14193:


In my original thought, this would be a missconfiguration.
How would you manage this? Adding it to the State Store?

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