[jira] [Commented] (MAPREDUCE-3458) Fix findbugs warnings in hadoop-examples
[ https://issues.apache.org/jira/browse/MAPREDUCE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162451#comment-13162451 ] Mahadev konar commented on MAPREDUCE-3458: -- +1, looks good. Good to see this, finally will have a clean test build! Fix findbugs warnings in hadoop-examples Key: MAPREDUCE-3458 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3458 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.1 Reporter: Arun C Murthy Assignee: Devaraj K Attachments: MAPREDUCE-3458.patch I see 12 findbugs warnings in hadoop-examples: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1336//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated MAPREDUCE-3485: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I just committed this. Thanks Ravi! DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3458) Fix findbugs warnings in hadoop-examples
[ https://issues.apache.org/jira/browse/MAPREDUCE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162457#comment-13162457 ] Hudson commented on MAPREDUCE-3458: --- Integrated in Hadoop-Hdfs-trunk-Commit #1434 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1434/]) MAPREDUCE-3458. Fix findbugs warnings in hadoop-examples. (Devaraj K via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210190 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support/findbugs-exclude.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/pom.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/Join.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/dancing/Pentomino.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraGen.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraInputFormat.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraSort.java Fix findbugs warnings in hadoop-examples Key: MAPREDUCE-3458 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3458 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.1 Reporter: Arun C Murthy Assignee: Devaraj K Fix For: 0.23.1 Attachments: MAPREDUCE-3458.patch I see 12 findbugs warnings in hadoop-examples: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1336//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3458) Fix findbugs warnings in hadoop-examples
[ https://issues.apache.org/jira/browse/MAPREDUCE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162460#comment-13162460 ] Hudson commented on MAPREDUCE-3458: --- Integrated in Hadoop-Common-0.23-Commit #251 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/251/]) MAPREDUCE-3458. Fix findbugs warnings in hadoop-examples. (Devaraj K via mahadev) - Merging r1210190 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210191 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support/findbugs-exclude.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/pom.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/Join.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/dancing/Pentomino.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraGen.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraInputFormat.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraSort.java Fix findbugs warnings in hadoop-examples Key: MAPREDUCE-3458 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3458 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.1 Reporter: Arun C Murthy Assignee: Devaraj K Fix For: 0.23.1 Attachments: MAPREDUCE-3458.patch I see 12 findbugs warnings in hadoop-examples: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1336//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162463#comment-13162463 ] Hudson commented on MAPREDUCE-3485: --- Integrated in Hadoop-Hdfs-0.23-Commit #242 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/242/]) MAPREDUCE-3485. DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS. (Ravi Gummadi via mahadev) - Merging r1210192 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210194 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerStatus.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3458) Fix findbugs warnings in hadoop-examples
[ https://issues.apache.org/jira/browse/MAPREDUCE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162462#comment-13162462 ] Hudson commented on MAPREDUCE-3458: --- Integrated in Hadoop-Hdfs-0.23-Commit #242 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/242/]) MAPREDUCE-3458. Fix findbugs warnings in hadoop-examples. (Devaraj K via mahadev) - Merging r1210190 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210191 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support/findbugs-exclude.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/pom.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/Join.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/dancing/Pentomino.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraGen.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraInputFormat.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraSort.java Fix findbugs warnings in hadoop-examples Key: MAPREDUCE-3458 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3458 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.1 Reporter: Arun C Murthy Assignee: Devaraj K Fix For: 0.23.1 Attachments: MAPREDUCE-3458.patch I see 12 findbugs warnings in hadoop-examples: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1336//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162469#comment-13162469 ] Hudson commented on MAPREDUCE-3485: --- Integrated in Hadoop-Hdfs-trunk-Commit #1435 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1435/]) MAPREDUCE-3485. DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS. (Ravi Gummadi via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210192 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerStatus.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162470#comment-13162470 ] Hudson commented on MAPREDUCE-3485: --- Integrated in Hadoop-Common-trunk-Commit #1361 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1361/]) MAPREDUCE-3485. DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS. (Ravi Gummadi via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210192 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerStatus.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162471#comment-13162471 ] Hudson commented on MAPREDUCE-3485: --- Integrated in Hadoop-Common-0.23-Commit #252 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/252/]) MAPREDUCE-3485. DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS. (Ravi Gummadi via mahadev) - Merging r1210192 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210194 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerStatus.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3458) Fix findbugs warnings in hadoop-examples
[ https://issues.apache.org/jira/browse/MAPREDUCE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162478#comment-13162478 ] Hudson commented on MAPREDUCE-3458: --- Integrated in Hadoop-Mapreduce-0.23-Commit #262 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/262/]) MAPREDUCE-3458. Fix findbugs warnings in hadoop-examples. (Devaraj K via mahadev) - Merging r1210190 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210191 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support/findbugs-exclude.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/pom.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/Join.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/dancing/Pentomino.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraGen.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraInputFormat.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraSort.java Fix findbugs warnings in hadoop-examples Key: MAPREDUCE-3458 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3458 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.1 Reporter: Arun C Murthy Assignee: Devaraj K Fix For: 0.23.1 Attachments: MAPREDUCE-3458.patch I see 12 findbugs warnings in hadoop-examples: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1336//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3458) Fix findbugs warnings in hadoop-examples
[ https://issues.apache.org/jira/browse/MAPREDUCE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162477#comment-13162477 ] Hudson commented on MAPREDUCE-3458: --- Integrated in Hadoop-Mapreduce-trunk-Commit #1385 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1385/]) MAPREDUCE-3458. Fix findbugs warnings in hadoop-examples. (Devaraj K via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210190 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/dev-support/findbugs-exclude.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/pom.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/Join.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/dancing/Pentomino.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraGen.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraInputFormat.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/terasort/TeraSort.java Fix findbugs warnings in hadoop-examples Key: MAPREDUCE-3458 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3458 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.1 Reporter: Arun C Murthy Assignee: Devaraj K Fix For: 0.23.1 Attachments: MAPREDUCE-3458.patch I see 12 findbugs warnings in hadoop-examples: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1336//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162490#comment-13162490 ] Hudson commented on MAPREDUCE-3485: --- Integrated in Hadoop-Mapreduce-trunk-Commit #1386 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1386/]) MAPREDUCE-3485. DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS. (Ravi Gummadi via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210192 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerStatus.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
[ https://issues.apache.org/jira/browse/MAPREDUCE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162495#comment-13162495 ] Hudson commented on MAPREDUCE-3485: --- Integrated in Hadoop-Mapreduce-0.23-Commit #263 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/263/]) MAPREDUCE-3485. DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS. (Ravi Gummadi via mahadev) - Merging r1210192 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1210194 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerStatus.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Assignee: Ravi Gummadi Fix For: 0.23.1 Attachments: 3485.patch, 3485.v1.patch With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3251) Network ACLs can prevent some clients to talk to MR ApplicationMaster
[
https://issues.apache.org/jira/browse/MAPREDUCE-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated MAPREDUCE-3251:
-
Status: Open (was: Patch Available)
Anupam,
Just took a look at the patch. Some questions/comments:
1. Can you please click on the box to grant license to Apache for code
inclusion for the next patch?
2. The code that create the Log.info() string should probably be a method on
its own:
I mean:
{noformat}
LOG.info(AppId: + application.getApplicationId()
++ # reserved containers:
++
application.getApplicationResourceUsageReport().getNumReservedContainers()
++ # used containers:
++
application.getApplicationResourceUsageReport().getNumUsedContainers()
++ Needed resources (memory):
++
application.getApplicationResourceUsageReport().getNeededResources().getMemory()
++ Rese
{noformat}
3. Does the test verify that we make sure we get the counters from jobhistory
once the job is done?
Network ACLs can prevent some clients to talk to MR ApplicationMaster
-
Key: MAPREDUCE-3251
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3251
Project: Hadoop Map/Reduce
Issue Type: Task
Components: mrv2
Affects Versions: 0.23.0
Reporter: Anupam Seth
Assignee: Anupam Seth
Priority: Critical
Fix For: 0.23.1
Attachments: MAPREDUCE-3251-branch_0_23.patch,
MAPREDUCE-3251_branch-0_23_preliminary.txt
In 0.20.xxx, the JobClient while polling goes to JT to get the job status.
With YARN, AM can be launched on any port and the client will have to have
ACL open to that port to talk to AM and get the job status. When the client
is within the same grid network access to AM is not a problem. But some
applications may have one installation per set of clusters and may launch
jobs even across such sets (on job trackers in another set of clusters). For
that to work only the JT port needs to be open currently. In case of YARN,
all ports will have to be opened up for things to work. That would be a
security no-no.
There are two possible solutions:
1) Make the job client only talk to RM (as an option) to get the job
status.
2) Limit the range of ports AM can listen on.
Option 2) may not be favorable as there is no direct OS API to find a free
port.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-3436) jobhistory link may be broken depending on the interface it is listening on
[
https://issues.apache.org/jira/browse/MAPREDUCE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmed Radwan reassigned MAPREDUCE-3436:
---
Assignee: Ahmed Radwan
jobhistory link may be broken depending on the interface it is listening on
---
Key: MAPREDUCE-3436
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3436
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: webapps
Affects Versions: 0.23.0, 0.23.1
Reporter: Bruno Mahé
Assignee: Ahmed Radwan
Labels: bigtop
On the following page : http://RESOURCE_MANAGER:8088/cluster/apps
There are links to the history for each application. None of them can be
reached since they all point to the ip 0.0.0.0. For instance:
http://0.0.0.0:8088/proxy/application_1321658790349_0002/jobhistory/job/job_1321658790349_2_2
Am I missing something?
[root@bigtop-fedora-15 ~]# jps
9968 ResourceManager
1495 NameNode
1645 DataNode
12935 Jps
11140 -- process information unavailable
5309 JobHistoryServer
10237 NodeManager
[root@bigtop-fedora-15 ~]# netstat -tlpn | grep 8088
tcp0 0 :::8088 :::*
LISTEN 9968/java
For reference, here is my configuration:
root@bigtop-fedora-15 ~]# cat /etc/yarn/conf/yarn-site.xml
?xml version=1.0?
configuration
!-- Site specific YARN configuration properties --
property
nameyarn.nodemanager.aux-services/name
valuemapreduce.shuffle/value
/property
property
nameyarn.nodemanager.aux-services.mapreduce.shuffle.class/name
valueorg.apache.hadoop.mapred.ShuffleHandler/value
/property
property
namemapreduce.admin.user.env/name
valueCLASSPATH=/etc/hadoop/conf/*:/usr/lib/hadoop/*:/usr/lib/hadoop/lib/*/value
/property
/configuration
[root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/hdfs-site.xml
?xml version=1.0?
configuration
property
namedfs.replication/name
value1/value
/property
property
namedfs.permissions/name
valuefalse/value
/property
property
!-- specify this so that running 'hadoop namenode -format' formats the
right dir --
namedfs.name.dir/name
value/var/lib/hadoop/cache/hadoop/dfs/name/value
/property
/configuration
[root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/core-site.xml
?xml version=1.0?
configuration
property
namefs.default.name/name
valuehdfs://localhost:8020/value
/property
property
namehadoop.tmp.dir/name
value/var/lib/hadoop/cache/${user.name}/value
/property
!-- OOZIE proxy user setting --
property
namehadoop.proxyuser.oozie.hosts/name
value*/value
/property
property
namehadoop.proxyuser.oozie.groups/name
value*/value
/property
/configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3436) jobhistory link may be broken depending on the interface it is listening on
[
https://issues.apache.org/jira/browse/MAPREDUCE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated MAPREDUCE-3436:
-
Component/s: mrv2
jobhistory link may be broken depending on the interface it is listening on
---
Key: MAPREDUCE-3436
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3436
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2, webapps
Affects Versions: 0.23.0, 0.23.1
Reporter: Bruno Mahé
Assignee: Ahmed Radwan
Labels: bigtop
On the following page : http://RESOURCE_MANAGER:8088/cluster/apps
There are links to the history for each application. None of them can be
reached since they all point to the ip 0.0.0.0. For instance:
http://0.0.0.0:8088/proxy/application_1321658790349_0002/jobhistory/job/job_1321658790349_2_2
Am I missing something?
[root@bigtop-fedora-15 ~]# jps
9968 ResourceManager
1495 NameNode
1645 DataNode
12935 Jps
11140 -- process information unavailable
5309 JobHistoryServer
10237 NodeManager
[root@bigtop-fedora-15 ~]# netstat -tlpn | grep 8088
tcp0 0 :::8088 :::*
LISTEN 9968/java
For reference, here is my configuration:
root@bigtop-fedora-15 ~]# cat /etc/yarn/conf/yarn-site.xml
?xml version=1.0?
configuration
!-- Site specific YARN configuration properties --
property
nameyarn.nodemanager.aux-services/name
valuemapreduce.shuffle/value
/property
property
nameyarn.nodemanager.aux-services.mapreduce.shuffle.class/name
valueorg.apache.hadoop.mapred.ShuffleHandler/value
/property
property
namemapreduce.admin.user.env/name
valueCLASSPATH=/etc/hadoop/conf/*:/usr/lib/hadoop/*:/usr/lib/hadoop/lib/*/value
/property
/configuration
[root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/hdfs-site.xml
?xml version=1.0?
configuration
property
namedfs.replication/name
value1/value
/property
property
namedfs.permissions/name
valuefalse/value
/property
property
!-- specify this so that running 'hadoop namenode -format' formats the
right dir --
namedfs.name.dir/name
value/var/lib/hadoop/cache/hadoop/dfs/name/value
/property
/configuration
[root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/core-site.xml
?xml version=1.0?
configuration
property
namefs.default.name/name
valuehdfs://localhost:8020/value
/property
property
namehadoop.tmp.dir/name
value/var/lib/hadoop/cache/${user.name}/value
/property
!-- OOZIE proxy user setting --
property
namehadoop.proxyuser.oozie.hosts/name
value*/value
/property
property
namehadoop.proxyuser.oozie.groups/name
value*/value
/property
/configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3398) Log Aggregation broken in Secure Mode
[ https://issues.apache.org/jira/browse/MAPREDUCE-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162563#comment-13162563 ] Hitesh Shah commented on MAPREDUCE-3398: assertTrue(Renewal of canceled token didn't fail, false); - could be replaced with a fail() spelling mistake - DelayedTokenCacneller Should we document that renewal/keep-alive time should always be 2x of node heartbeat time? Apart from the above minor nits, patch looks good. Log Aggregation broken in Secure Mode - Key: MAPREDUCE-3398 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3398 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2, nodemanager Affects Versions: 0.23.0 Reporter: Siddharth Seth Assignee: Siddharth Seth Priority: Critical Fix For: 0.23.1 Attachments: MR3398_v1.txt Log aggregation in secure mode does not work with MAPREDUCE-2977. The nodemanager relies on the users credentials to write out logs to HDFS. These credentials are currently cancelled once a job completes, before the NM can write out the logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3436) jobhistory link may be broken depending on the interface it is listening on
[
https://issues.apache.org/jira/browse/MAPREDUCE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162567#comment-13162567
]
Ahmed Radwan commented on MAPREDUCE-3436:
-
Bruno, I checked this issue, the default mapreduce jobhistory webapp address is
set to 0.0.0.0:19888, and this is why you are hitting this link problem. Can
you try setting the property: mapreduce.jobhistory.webapp.address in your
cluster conf files hsAddress:port, hsAddress is where you started your
history server, and choose any port of your choice (doesn't need to be the
default 19888). Can you try that?
jobhistory link may be broken depending on the interface it is listening on
---
Key: MAPREDUCE-3436
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3436
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2, webapps
Affects Versions: 0.23.0, 0.23.1
Reporter: Bruno Mahé
Assignee: Ahmed Radwan
Labels: bigtop
On the following page : http://RESOURCE_MANAGER:8088/cluster/apps
There are links to the history for each application. None of them can be
reached since they all point to the ip 0.0.0.0. For instance:
http://0.0.0.0:8088/proxy/application_1321658790349_0002/jobhistory/job/job_1321658790349_2_2
Am I missing something?
[root@bigtop-fedora-15 ~]# jps
9968 ResourceManager
1495 NameNode
1645 DataNode
12935 Jps
11140 -- process information unavailable
5309 JobHistoryServer
10237 NodeManager
[root@bigtop-fedora-15 ~]# netstat -tlpn | grep 8088
tcp0 0 :::8088 :::*
LISTEN 9968/java
For reference, here is my configuration:
root@bigtop-fedora-15 ~]# cat /etc/yarn/conf/yarn-site.xml
?xml version=1.0?
configuration
!-- Site specific YARN configuration properties --
property
nameyarn.nodemanager.aux-services/name
valuemapreduce.shuffle/value
/property
property
nameyarn.nodemanager.aux-services.mapreduce.shuffle.class/name
valueorg.apache.hadoop.mapred.ShuffleHandler/value
/property
property
namemapreduce.admin.user.env/name
valueCLASSPATH=/etc/hadoop/conf/*:/usr/lib/hadoop/*:/usr/lib/hadoop/lib/*/value
/property
/configuration
[root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/hdfs-site.xml
?xml version=1.0?
configuration
property
namedfs.replication/name
value1/value
/property
property
namedfs.permissions/name
valuefalse/value
/property
property
!-- specify this so that running 'hadoop namenode -format' formats the
right dir --
namedfs.name.dir/name
value/var/lib/hadoop/cache/hadoop/dfs/name/value
/property
/configuration
[root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/core-site.xml
?xml version=1.0?
configuration
property
namefs.default.name/name
valuehdfs://localhost:8020/value
/property
property
namehadoop.tmp.dir/name
value/var/lib/hadoop/cache/${user.name}/value
/property
!-- OOZIE proxy user setting --
property
namehadoop.proxyuser.oozie.hosts/name
value*/value
/property
property
namehadoop.proxyuser.oozie.groups/name
value*/value
/property
/configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-3507) Remove Cluster as a public API on the client side.
Remove Cluster as a public API on the client side. -- Key: MAPREDUCE-3507 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3507 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Reporter: Mahadev konar Fix For: 0.23.1 This has been a major source of grief for me when fixing MAPREDUCE-3443 and MAPREDUCE-3380. The public API of cluster is very confusing and doesnt add any value to the client side. This has caused more confusion with the current jobclient/job/cluster interaction currently in the code base. It would be best to make this private before folks actually start using it and we will end up supporting this broken API for a long time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2863) Support web-services for RM NM
[ https://issues.apache.org/jira/browse/MAPREDUCE-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162583#comment-13162583 ] Hitesh Shah commented on MAPREDUCE-2863: Comments - some files show unused imports - there are still quite some null checks on objects when initialized via object constructors. In some cases, there are no try catch blocks hence these null checks will never get triggered in any case as the ctor will likely throw exceptions. In other cases, there is a null check after the try catch block i.e. dead code. Something to look into - not sure if this is caused by the framework. I came across http://java.net/jira/browse/JERSEY-38 but not sure whether it is related to the issue below yet. - http://hrt11n07.cc1.ygridcore.net:8088/ws/v1/cluster/nodes/ returns a 404. - http://hrt11n07.cc1.ygridcore.net:8088/ws/v1/cluster/nodes returns data. ( likely an issue with all resources ) General question on absent applications - querying for an absent app i.e. say http://RM:8088/proxy/application_1323054018624_0004/ws/v1/mapreduce/info - returns a 500 with a stack trace instead of a 404. From an api spec point of view, this is not really an error but just a not found. Support web-services for RM NM Key: MAPREDUCE-2863 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2863 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2, nodemanager, resourcemanager Affects Versions: 0.23.0 Reporter: Arun C Murthy Assignee: Thomas Graves Priority: Blocker Attachments: MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, amoutput.txt, appoutput.txt, hsoutput.txt, nmoutput.txt, nmoutput.txt, nmoutput.txt, rmoutput.txt, rmoutput.txt, rmoutput.txt It will be very useful for RM and NM to support web-services to export json/xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2863) Support web-services for RM NM
[ https://issues.apache.org/jira/browse/MAPREDUCE-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162584#comment-13162584 ] Hitesh Shah commented on MAPREDUCE-2863: Also, given that webhdfs is using json, defaulting to json may be the right option to go with. Support web-services for RM NM Key: MAPREDUCE-2863 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2863 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2, nodemanager, resourcemanager Affects Versions: 0.23.0 Reporter: Arun C Murthy Assignee: Thomas Graves Priority: Blocker Attachments: MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, amoutput.txt, appoutput.txt, hsoutput.txt, nmoutput.txt, nmoutput.txt, nmoutput.txt, rmoutput.txt, rmoutput.txt, rmoutput.txt It will be very useful for RM and NM to support web-services to export json/xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3363) The totalnodes and memorytotal fields show wrong information if the nodes are going down and coming up early(before 10min)
[ https://issues.apache.org/jira/browse/MAPREDUCE-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162607#comment-13162607 ] Devaraj K commented on MAPREDUCE-3363: -- This issue will cause a huge loss, if multiple nodes restart at a time, and due to the false cluster capacity assumed, many jobs will fail in the cluster, which is a performance hit. The totalnodes and memorytotal fields show wrong information if the nodes are going down and coming up early(before 10min) Key: MAPREDUCE-3363 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3363 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.24.0 Reporter: Ramgopal N Assignee: Devaraj K Attachments: Applications.htm, screenshot-1.jpg The node details is not moved from Totalnodes to lostnodes for 60 ms.So if the node is going down and coming up before the expiry interval, the cluster status in terms of the total nodes and Total cluster memory displays wrong values. Atleast, if the same node is coming up again...should not consider as new node.No point of time duplicate nodes should be displayed in Totalnodes list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-3494) The RM should handle the graceful shutdown of the NM.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K reassigned MAPREDUCE-3494: Assignee: Devaraj K The RM should handle the graceful shutdown of the NM. - Key: MAPREDUCE-3494 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3494 Project: Hadoop Map/Reduce Issue Type: Bug Components: nodemanager, resourcemanager Reporter: Ravi Teja Ch N V Assignee: Devaraj K Instead of waiting for the NM expiry, RM should remove and handle the NM, which is shutdown gracefully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
