[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248252#comment-16248252 ] Hudson commented on HDFS-12498: --- ABORTED: Integrated in Jenkins build Hadoop-trunk-Commit #13221 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13221/]) HDFS-12498. Journal Syncer is not started in Federated + HA cluster. (arp: rev 6d201f77c734d6c6a9e3e297fe3dbff251cbb8b3) * (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/JournalNodeSyncer.java * (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/qjournal/server/TestJournalNode.java > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Fix For: 3.1.0 > > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, HDFS-12498.05.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236152#comment-16236152 ] Bharat Viswanadham commented on HDFS-12498: --- Test case failures are not related to this patch. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham >Priority: Major > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, HDFS-12498.05.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16227493#comment-16227493 ] Hadoop QA commented on HDFS-12498: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 9m 38s{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} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m 45s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 54s{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} 1m 3s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 11m 23s{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 58s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 46s{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 51s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 51s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 34s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 55s{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} 11m 3s{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} 2m 5s{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} 88m 9s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 23s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}147m 31s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hdfs.TestEncryptionZones | | | hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting | | | hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 | | JIRA Issue | HDFS-12498 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12894808/HDFS-12498.05.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux acfadca45c97 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 5f681fa | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_131 | | findbugs | v3.1.0-RC1 | | unit | https://builds.apache.org/job/PreCommit-HDFS-Build/21899/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt | | Test Results | https://builds.apache.org/job/PreCommit-HDFS-Build/21899/testReport/ | | modules | C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/21899/console |
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225441#comment-16225441 ] Arpit Agarwal commented on HDFS-12498: -- +1 for the v05 patch, pending Jenkins. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, HDFS-12498.05.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225424#comment-16225424 ] Bharat Viswanadham commented on HDFS-12498: --- [~arpitagarwal] Fixed checkstyle issues. [~hanishakoneru] Thank You for review. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, HDFS-12498.05.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225404#comment-16225404 ] Hanisha Koneru commented on HDFS-12498: --- Yes. Patch v04 LGTM. Thanks. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224109#comment-16224109 ] Arpit Agarwal commented on HDFS-12498: -- Thanks [~bharatviswa]. The v4 patch lgtm. Could you please check that the checkstyle comments are valid? [~hanishakoneru], are you okay with latest patch? > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223196#comment-16223196 ] Hadoop QA commented on HDFS-12498: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 17s{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} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 13m 25s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 51s{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 58s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 10m 16s{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 48s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 51s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 48s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 48s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 35s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch generated 8 new + 15 unchanged - 0 fixed = 23 total (was 15) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 54s{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 57s{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} 2m 1s{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}116m 38s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 21s{color} | {color:red} The patch generated 3 ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}161m 33s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hdfs.server.namenode.ha.TestPipelinesFailover | | | hadoop.hdfs.server.namenode.ha.TestDNFencingWithReplication | | | hadoop.hdfs.TestSafeModeWithStripedFile | | Timed out junit tests | org.apache.hadoop.hdfs.TestLeaseRecovery2 | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 | | JIRA Issue | HDFS-12498 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12894474/HDFS-12498.04.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 1433f431b08a 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 8be5707 | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_131 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-HDFS-Build/21858/artifact/out/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt | | unit |
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222968#comment-16222968 ] Bharat Viswanadham commented on HDFS-12498: --- Attached patch v04 to address review comments in the review board. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, > HDFS-12498.03.patch, HDFS-12498.04.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181511#comment-16181511 ] Hadoop QA commented on HDFS-12498: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 20s{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} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 14m 34s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 43s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 1s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 10m 44s{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 42s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 51s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 47s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 34s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch generated 4 new + 85 unchanged - 0 fixed = 89 total (was 85) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 53s{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 55s{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 57s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 43s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red} 91m 15s{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}137m 23s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hdfs.qjournal.server.TestJournalNodeSync | | | hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting | | | hadoop.hdfs.server.namenode.TestReencryption | | | hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery | \\ \\ || Subsystem || Report/Notes || | Docker | Image:yetus/hadoop:71bbb86 | | JIRA Issue | HDFS-12498 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12888912/HDFS-12498.02.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux dd4d3ae5c49a 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 1267ff2 | | Default Java | 1.8.0_144 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-HDFS-Build/21362/artifact/patchprocess/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt | | unit | https://builds.apache.org/job/PreCommit-HDFS-Build/21362/artifact/patchprocess/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt | | Test
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179700#comment-16179700 ] Hadoop QA commented on HDFS-12498: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 59s{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} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m 42s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 54s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 39s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 0s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 45s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 39s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 52s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 49s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 36s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch generated 4 new + 85 unchanged - 0 fixed = 89 total (was 85) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 55s{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} findbugs {color} | {color:green} 1m 48s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red}115m 39s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 18s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}144m 37s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting | | | hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery | | | hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure | | | hadoop.hdfs.TestRollingUpgrade | | | hadoop.hdfs.TestReadStripedFileWithMissingBlocks | \\ \\ || Subsystem || Report/Notes || | Docker | Image:yetus/hadoop:71bbb86 | | JIRA Issue | HDFS-12498 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12888912/HDFS-12498.02.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle | | uname | Linux 2ec8c29afc27 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31 14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh | | git revision | trunk / e928ee5 | | Default Java | 1.8.0_144 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-HDFS-Build/21344/artifact/patchprocess/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt | | unit | https://builds.apache.org/job/PreCommit-HDFS-Build/21344/artifact/patchprocess/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt | | Test Results | https://builds.apache.org/job/PreCommit-HDFS-Build/21344/testReport/ | | modules | C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/21344/console | | Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org | This message was
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179638#comment-16179638 ] Bharat Viswanadham commented on HDFS-12498: --- {code:java} In DFSUtil#getJournalNodeAddresses(), we first convert the qjournal uri to a set of journal node InetSocketAddress's and then convert that to Set. In JournalNodeSyncer#getOtherJournalNodeAddrs(), this Set of journal node address's is again converted to InetSocketAddress's. We should avoid the double work here. DFSUtil#getJournalNodeAddresses() can be broken down into two methods: Set getJournalNodeSocketAddresses(Configuration conf); Set getJournalNodeAddresses(Configuration conf); {code} [~hanishakoneru] I have also thought about this. but if i add another method for this, it will be a lot of common code among these methods. I have done this, so that I can reuse the most of the existing code. And also even if this conversion is done, this is a one time thing, only it will be done during journal node startup. Let me know your thoughts on this. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179561#comment-16179561 ] Hanisha Koneru commented on HDFS-12498: --- Thanks [~bharatviswa] for the patch. Few comments: - In {{DFSUtil#getJournalNodeAddresses()}}, we first convert the qjournal uri to a set of journal node InetSocketAddress's and then convert that to Set. In {{JournalNodeSyncer#getOtherJournalNodeAddrs()}}, this _Set_ of journal node address's is again converted to InetSocketAddress's. We should avoid the double work here. {{DFSUtil#getJournalNodeAddresses()}} can be broken down into two methods: {quote} Set getJournalNodeSocketAddresses(Configuration conf); Set getJournalNodeAddresses(Configuration conf); {quote} The second method can be called from {{GetConf}} and the first one from {{JournalNodeSyncer}}. No need for the new _portrequired_ variable also. - The following piece of code in {{DFSUtil#getJournalNodeAddresses()}} can be optimized by using the _List#remove()_ method instead of _List#removeAll()_ method (as only one element is removed). {code} journalnodeSocketAddressList.removeAll(Sets.newHashSet(jn.getBoundIpcAddress())); {code} > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179428#comment-16179428 ] Bharat Viswanadham commented on HDFS-12498: --- Now if dfs.shared.edits.dir is suffixed with nameserviceId or (namserviceId along with namenodeId) journal syncer is getting started. Tested it on federated cluster setup. > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177482#comment-16177482 ] Hadoop QA commented on HDFS-12498: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 11s{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} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 13m 34s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 38s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 55s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 40s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 41s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 27s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 26s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 26s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 33s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch generated 2 new + 85 unchanged - 0 fixed = 87 total (was 85) {color} | | {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m 28s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 27s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 39s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 26s{color} | {color:red} hadoop-hdfs in the patch failed. {color} | | {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 14s{color} | {color:red} The patch generated 1 ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 23m 23s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Image:yetus/hadoop:71bbb86 | | JIRA Issue | HDFS-12498 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12888633/HDFS-12498.01.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle | | uname | Linux 0bc4c2f6c619 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh | | git revision | trunk / cda3378 | | Default Java | 1.8.0_144 | | findbugs | v3.1.0-RC1 | | mvninstall | https://builds.apache.org/job/PreCommit-HDFS-Build/21318/artifact/patchprocess/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt | | compile | https://builds.apache.org/job/PreCommit-HDFS-Build/21318/artifact/patchprocess/patch-compile-hadoop-hdfs-project_hadoop-hdfs.txt | | javac | https://builds.apache.org/job/PreCommit-HDFS-Build/21318/artifact/patchprocess/patch-compile-hadoop-hdfs-project_hadoop-hdfs.txt | | checkstyle | https://builds.apache.org/job/PreCommit-HDFS-Build/21318/artifact/patchprocess/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt | | mvnsite | https://builds.apache.org/job/PreCommit-HDFS-Build/21318/artifact/patchprocess/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt | | findbugs | https://builds.apache.org/job/PreCommit-HDFS-Build/21318/artifact/patchprocess/patch-findbugs-hadoop-hdfs-project_hadoop-hdfs.txt | | unit |
[jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster
[ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175611#comment-16175611 ] Bharat Viswanadham commented on HDFS-12498: --- As HDFS-12486 is used to get journal node list, the fix can be used here to call the method DFSUtil.getJournalNodeAddresses and get list of journalnodes and pass them to getOtherJournalNodeProxies() > Journal Syncer is not started in Federated + HA cluster > --- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when > dfs.shared.edits.dir.<> is provided, instead of > dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct > Shared Edits Uri > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode > addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN > org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start > SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org