[jira] [Commented] (MAPREDUCE-3532) When 0 is provided as port number in yarn.nodemanager.webapp.address, NMs webserver component picks up random port, NM keeps on Reporting 0 port to RM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186187#comment-13186187 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Hdfs-trunk #925 (See

[jira] [Commented] (MAPREDUCE-3656) Sort job on 350 scale is consistently failing with latest MRV2 code

[ https://issues.apache.org/jira/browse/MAPREDUCE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186189#comment-13186189 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Hdfs-trunk #925 (See

[jira] [Commented] (MAPREDUCE-3596) Sort benchmark got hang after completion of 99% map phase

[ https://issues.apache.org/jira/browse/MAPREDUCE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186188#comment-13186188 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Hdfs-trunk #925 (See

[jira] [Commented] (MAPREDUCE-3404) Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false

[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186190#comment-13186190 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Hdfs-trunk #925 (See

[jira] [Commented] (MAPREDUCE-3532) When 0 is provided as port number in yarn.nodemanager.webapp.address, NMs webserver component picks up random port, NM keeps on Reporting 0 port to RM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186191#comment-13186191 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Hdfs-0.23-Build #138 (See

[jira] [Commented] (MAPREDUCE-3596) Sort benchmark got hang after completion of 99% map phase

[ https://issues.apache.org/jira/browse/MAPREDUCE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186192#comment-13186192 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Hdfs-0.23-Build #138 (See

[jira] [Commented] (MAPREDUCE-3404) Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false

[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186194#comment-13186194 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Hdfs-0.23-Build #138 (See

[jira] [Commented] (MAPREDUCE-3656) Sort job on 350 scale is consistently failing with latest MRV2 code

[ https://issues.apache.org/jira/browse/MAPREDUCE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186193#comment-13186193 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Hdfs-0.23-Build #138 (See

[jira] [Commented] (MAPREDUCE-3596) Sort benchmark got hang after completion of 99% map phase

[ https://issues.apache.org/jira/browse/MAPREDUCE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186198#comment-13186198 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Mapreduce-0.23-Build #160

[jira] [Commented] (MAPREDUCE-3532) When 0 is provided as port number in yarn.nodemanager.webapp.address, NMs webserver component picks up random port, NM keeps on Reporting 0 port to RM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186197#comment-13186197 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Mapreduce-0.23-Build #160

[jira] [Commented] (MAPREDUCE-3656) Sort job on 350 scale is consistently failing with latest MRV2 code

[ https://issues.apache.org/jira/browse/MAPREDUCE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186199#comment-13186199 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Mapreduce-0.23-Build #160

[jira] [Commented] (MAPREDUCE-3404) Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false

[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186200#comment-13186200 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Mapreduce-0.23-Build #160

[jira] [Commented] (MAPREDUCE-3532) When 0 is provided as port number in yarn.nodemanager.webapp.address, NMs webserver component picks up random port, NM keeps on Reporting 0 port to RM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186204#comment-13186204 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Mapreduce-trunk #958 (See

[jira] [Commented] (MAPREDUCE-3596) Sort benchmark got hang after completion of 99% map phase

[ https://issues.apache.org/jira/browse/MAPREDUCE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186205#comment-13186205 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Mapreduce-trunk #958 (See

[jira] [Commented] (MAPREDUCE-3656) Sort job on 350 scale is consistently failing with latest MRV2 code

[ https://issues.apache.org/jira/browse/MAPREDUCE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186206#comment-13186206 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Mapreduce-trunk #958 (See

[jira] [Commented] (MAPREDUCE-3404) Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false

[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186207#comment-13186207 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Mapreduce-trunk #958 (See

[jira] [Updated] (MAPREDUCE-3641) CapacityScheduler should be more conservative assigning off-switch requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-3641: - Status: Patch Available (was: Open) Writing unit tests now...

[jira] [Updated] (MAPREDUCE-3641) CapacityScheduler should be more conservative assigning off-switch requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-3641: - Attachment: MAPREDUCE-3641.patch Ok, tested patch on secure cluster.

[jira] [Commented] (MAPREDUCE-3641) CapacityScheduler should be more conservative assigning off-switch requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13186400#comment-13186400 ] Hadoop QA commented on MAPREDUCE-3641: -- -1 overall. Here are the results of

[jira] [Moved] (MAPREDUCE-3673) org.apache.hadoop.mapreduce.lib.chain.ChainMapper missing on 1.0

[ https://issues.apache.org/jira/browse/MAPREDUCE-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J moved HADOOP-7969 to MAPREDUCE-3673: Component/s: (was: build) mrv1

[jira] [Resolved] (MAPREDUCE-3673) org.apache.hadoop.mapreduce.lib.chain.ChainMapper missing on 1.0

[ https://issues.apache.org/jira/browse/MAPREDUCE-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-3673. Resolution: Duplicate 1.0 does not contain the entire set of mapred.lib.* ported to new API.