[jira] [Commented] (HDFS-13138) webhdfs of federated namenode does not work properly
[
https://issues.apache.org/jira/browse/HDFS-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374300#comment-16374300
]
genericqa commented on HDFS-13138:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 11m
16s{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} branch-2.7 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
2s{color} | {color:green} branch-2.7 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
6s{color} | {color:green} branch-2.7 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s{color} | {color:green} branch-2.7 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
3s{color} | {color:green} branch-2.7 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
0s{color} | {color:green} branch-2.7 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
48s{color} | {color:green} branch-2.7 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 23s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch
generated 1 new + 184 unchanged - 0 fixed = 185 total (was 184) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 60 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
46s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}205m 30s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 2m
38s{color} | {color:red} The patch generated 246 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black}244m 49s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Unreaped Processes | hadoop-hdfs:52 |
| Failed junit tests | hadoop.hdfs.TestFsShellPermission |
| | hadoop.hdfs.TestDistributedFileSystem |
| Timed out junit tests | org.apache.hadoop.hdfs.TestEncryptionZones |
| | org.apache.hadoop.hdfs.TestLeaseRecovery2 |
| | org.apache.hadoop.hdfs.tools.TestDFSAdminWithHA |
| | org.apache.hadoop.hdfs.qjournal.client.TestQuorumJournalManager |
| | org.apache.hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer |
| | org.apache.hadoop.hdfs.tools.offlineEditsViewer.TestOfflineEditsViewer |
| | org.apache.hadoop.hdfs.TestDatanodeRegistration |
| | org.apache.hadoop.hdfs.TestDFSClientFailover |
| | org.apache.hadoop.hdfs.TestSetrepDecreasing |
| | org.apache.hadoop.hdfs.TestReplaceDatanodeOnFailure |
| | org.apache.hadoop.hdfs.qjournal.server.TestJournalNode |
| | org.apache.hadoop.hdfs.TestQuota |
| | org.apache.hadoop.hdfs.TestDataTransferKeepalive |
| | org.apache.hadoop.hdfs.TestDatanodeDeath |
| | org.apache.hadoop.hdfs.TestFileLengthOnClusterRestart |
| | org.apache.hadoop.hdfs.TestFileAppend |
| | org.apache.hadoop.hdfs.TestPread |
| | org.apache.hadoop.hdfs.TestSafeMode |
| | org.apache.hadoop.hdfs.TestFileAppend4 |
| | org.apache.hadoop.hdfs.TestDFSFinalize |
| | org.apache.hadoop.hdfs.qjournal.client.TestQJMWithFaults |
| | org.apache.hadoop.hdfs.TestDFSUpgradeFromImage |
| | org.apache.hadoop.hdfs.web.TestWebHdfsTokens |
| | org.apache.hadoop.hdfs.security.Test
[jira] [Commented] (HDFS-13138) webhdfs of federated namenode does not work properly
[
https://issues.apache.org/jira/browse/HDFS-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374078#comment-16374078
]
KWON BYUNGCHANG commented on HDFS-13138:
I modified some issues. and attached patch.
> webhdfs of federated namenode does not work properly
> -
>
> Key: HDFS-13138
> URL: https://issues.apache.org/jira/browse/HDFS-13138
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
>Affects Versions: 2.7.1, 3.0.0
>Reporter: KWON BYUNGCHANG
>Priority: Major
> Attachments: HDFS-13138.001.branch-2.7.patch, HDFS-13138.001.patch,
> HDFS-13138.002.branch-2.7.patch, HDFS-13138.002.patch,
> HDFS-13138.003.branch-2.7.patch, HDFS-13138.003.patch
>
>
> my cluster has multiple namenodes using HDFS Federation.
> webhdfs that is not defaultFS does not work properly.
> when I uploaded to non defaultFS namenode using webhdfs.
> uploaded file was founded at defaultFS namenode.
>
> I think root cause is that
> clientNamenodeAddress of non defaultFS namenode is always fs.defaultFS.
>
> [https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java#L462]
>
> {code:java}
> /**
>* Set the namenode address that will be used by clients to access this
>* namenode or name service. This needs to be called before the config
>* is overriden.
>*/
> public void setClientNamenodeAddress(Configuration conf) {
> String nnAddr = conf.get(FS_DEFAULT_NAME_KEY);
> if (nnAddr == null) {
> // default fs is not set.
> clientNamenodeAddress = null;
> return;
> }
> LOG.info("{} is {}", FS_DEFAULT_NAME_KEY, nnAddr);
> URI nnUri = URI.create(nnAddr);
> String nnHost = nnUri.getHost();
> if (nnHost == null) {
> clientNamenodeAddress = null;
> return;
> }
> if (DFSUtilClient.getNameServiceIds(conf).contains(nnHost)) {
> // host name is logical
> clientNamenodeAddress = nnHost;
> } else if (nnUri.getPort() > 0) {
> // physical address with a valid port
> clientNamenodeAddress = nnUri.getAuthority();
> } else {
> // the port is missing or 0. Figure out real bind address later.
> clientNamenodeAddress = null;
> return;
> }
> LOG.info("Clients are to use {} to access"
> + " this namenode/service.", clientNamenodeAddress );
> }
> {code}
>
> so webhdfs is redirected to datanode having wrong namenoderpcaddress parameter
> finally file was located namenode of fs,defaultFS
>
> workaround is
> configure fs.defaultFS of each namenode to its own nameservice.
> e.g.
> hdfs://ns1 has fs.defaultFS=hdfs://ns1
> hdfs://ns2 has fs.defaultFS=hdfs://ns2
>
>
>
>
>
--
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-13138) webhdfs of federated namenode does not work properly
[
https://issues.apache.org/jira/browse/HDFS-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363493#comment-16363493
]
genericqa commented on HDFS-13138:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 7m
6s{color} | {color:red} Docker failed to build yetus/hadoop:ea57d10. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-13138 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12910504/HDFS-13138.002.branch-2.7.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/23058/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> webhdfs of federated namenode does not work properly
> -
>
> Key: HDFS-13138
> URL: https://issues.apache.org/jira/browse/HDFS-13138
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
>Affects Versions: 2.7.1, 3.0.0
>Reporter: KWON BYUNGCHANG
>Priority: Major
> Attachments: HDFS-13138.001.branch-2.7.patch, HDFS-13138.001.patch,
> HDFS-13138.002.branch-2.7.patch, HDFS-13138.002.patch
>
>
> my cluster has multiple namenodes using HDFS Federation.
> webhdfs that is not defaultFS does not work properly.
> when I uploaded to non defaultFS namenode using webhdfs.
> uploaded file was founded at defaultFS namenode.
>
> I think root cause is that
> clientNamenodeAddress of non defaultFS namenode is always fs.defaultFS.
>
> [https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java#L462]
>
> {code:java}
> /**
>* Set the namenode address that will be used by clients to access this
>* namenode or name service. This needs to be called before the config
>* is overriden.
>*/
> public void setClientNamenodeAddress(Configuration conf) {
> String nnAddr = conf.get(FS_DEFAULT_NAME_KEY);
> if (nnAddr == null) {
> // default fs is not set.
> clientNamenodeAddress = null;
> return;
> }
> LOG.info("{} is {}", FS_DEFAULT_NAME_KEY, nnAddr);
> URI nnUri = URI.create(nnAddr);
> String nnHost = nnUri.getHost();
> if (nnHost == null) {
> clientNamenodeAddress = null;
> return;
> }
> if (DFSUtilClient.getNameServiceIds(conf).contains(nnHost)) {
> // host name is logical
> clientNamenodeAddress = nnHost;
> } else if (nnUri.getPort() > 0) {
> // physical address with a valid port
> clientNamenodeAddress = nnUri.getAuthority();
> } else {
> // the port is missing or 0. Figure out real bind address later.
> clientNamenodeAddress = null;
> return;
> }
> LOG.info("Clients are to use {} to access"
> + " this namenode/service.", clientNamenodeAddress );
> }
> {code}
>
> so webhdfs is redirected to datanode having wrong namenoderpcaddress parameter
> finally file was located namenode of fs,defaultFS
>
> workaround is
> configure fs.defaultFS of each namenode to its own nameservice.
> e.g.
> hdfs://ns1 has fs.defaultFS=hdfs://ns1
> hdfs://ns2 has fs.defaultFS=hdfs://ns2
>
>
>
>
>
--
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-13138) webhdfs of federated namenode does not work properly
[
https://issues.apache.org/jira/browse/HDFS-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363487#comment-16363487
]
KWON BYUNGCHANG commented on HDFS-13138:
initial patch crashed with hadoop.hdfs.web.TestWebHdfsFileSystemContract. I
fixed.
other test crash does not related with this issue.
> webhdfs of federated namenode does not work properly
> -
>
> Key: HDFS-13138
> URL: https://issues.apache.org/jira/browse/HDFS-13138
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
>Affects Versions: 2.7.1, 3.0.0
>Reporter: KWON BYUNGCHANG
>Priority: Major
> Attachments: HDFS-13138.001.branch-2.7.patch, HDFS-13138.001.patch,
> HDFS-13138.002.patch
>
>
> my cluster has multiple namenodes using HDFS Federation.
> webhdfs that is not defaultFS does not work properly.
> when I uploaded to non defaultFS namenode using webhdfs.
> uploaded file was founded at defaultFS namenode.
>
> I think root cause is that
> clientNamenodeAddress of non defaultFS namenode is always fs.defaultFS.
>
> [https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java#L462]
>
> {code:java}
> /**
>* Set the namenode address that will be used by clients to access this
>* namenode or name service. This needs to be called before the config
>* is overriden.
>*/
> public void setClientNamenodeAddress(Configuration conf) {
> String nnAddr = conf.get(FS_DEFAULT_NAME_KEY);
> if (nnAddr == null) {
> // default fs is not set.
> clientNamenodeAddress = null;
> return;
> }
> LOG.info("{} is {}", FS_DEFAULT_NAME_KEY, nnAddr);
> URI nnUri = URI.create(nnAddr);
> String nnHost = nnUri.getHost();
> if (nnHost == null) {
> clientNamenodeAddress = null;
> return;
> }
> if (DFSUtilClient.getNameServiceIds(conf).contains(nnHost)) {
> // host name is logical
> clientNamenodeAddress = nnHost;
> } else if (nnUri.getPort() > 0) {
> // physical address with a valid port
> clientNamenodeAddress = nnUri.getAuthority();
> } else {
> // the port is missing or 0. Figure out real bind address later.
> clientNamenodeAddress = null;
> return;
> }
> LOG.info("Clients are to use {} to access"
> + " this namenode/service.", clientNamenodeAddress );
> }
> {code}
>
> so webhdfs is redirected to datanode having wrong namenoderpcaddress parameter
> finally file was located namenode of fs,defaultFS
>
> workaround is
> configure fs.defaultFS of each namenode to its own nameservice.
> e.g.
> hdfs://ns1 has fs.defaultFS=hdfs://ns1
> hdfs://ns2 has fs.defaultFS=hdfs://ns2
>
>
>
>
>
--
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-13138) webhdfs of federated namenode does not work properly
[
https://issues.apache.org/jira/browse/HDFS-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362226#comment-16362226
]
genericqa commented on HDFS-13138:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{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 2 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m
38s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
50s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
37s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
53s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
9m 53s{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} 1m
47s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
50s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 46s{color}
| {color:red} hadoop-hdfs-project_hadoop-hdfs generated 1 new + 391 unchanged -
0 fixed = 392 total (was 391) {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 32s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch
generated 2 new + 304 unchanged - 0 fixed = 306 total (was 304) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
52s{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}
9m 21s{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
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 87m 14s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}133m 11s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hdfs.web.TestWebHdfsFileSystemContract |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure |
| | hadoop.hdfs.TestDistributedFileSystemWithECFile |
| | hadoop.hdfs.TestDFSStripedInputStream |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure030 |
| | hadoop.hdfs.web.TestWebHdfsTimeouts |
| | hadoop.hdfs.TestErasureCodingPolicies |
| | hadoop.hdfs.TestFSOutputSummer |
| | hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure |
| | hadoop.hdfs.TestDecommission |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure140 |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | HDFS-13138 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12910369/HDFS-13138.001.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit shadedclient findbugs checkstyle |
| uname | Linux e1e0d202b737 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precom
