[jira] [Updated] (MAPREDUCE-3597) Provide a way to access other info of history file from Rumentool

[ https://issues.apache.org/jira/browse/MAPREDUCE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Gummadi updated MAPREDUCE-3597: Attachment: 3597.branch-1.v1.patch Attaching patch for branch-1.

[jira] [Commented] (MAPREDUCE-3664) HDFS Federation Documentation has incorrect configuration example

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

[jira] [Commented] (MAPREDUCE-3545) Remove Avro RPC

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

[jira] [Commented] (MAPREDUCE-3597) Provide a way to access other info of history file from Rumentool

[ https://issues.apache.org/jira/browse/MAPREDUCE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185576#comment-13185576 ] Amar Kamat commented on MAPREDUCE-3597: --- The patch looks good to me. It seems

[jira] [Commented] (MAPREDUCE-3545) Remove Avro RPC

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

[jira] [Commented] (MAPREDUCE-3664) HDFS Federation Documentation has incorrect configuration example

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

[jira] [Created] (MAPREDUCE-3667) Gridmix jobs are failing with OOM in reduce shuffle phase.

Gridmix jobs are failing with OOM in reduce shuffle phase. -- Key: MAPREDUCE-3667 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3667 Project: Hadoop Map/Reduce Issue Type: Bug

[jira] [Updated] (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:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3656: -- Status: Open (was: Patch Available) Cancelling patch. Needs another fix. Sort is

[jira] [Updated] (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:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3656: -- Attachment: MR3656.txt Yet another patch. Hopefully this one has everything

[jira] [Updated] (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:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3656: -- Status: Patch Available (was: Open) Sort job on 350 scale is consistently

[jira] [Created] (MAPREDUCE-3668) AccessControlException when running mapred job -list command

AccessControlException when running mapred job -list command Key: MAPREDUCE-3668 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3668 Project: Hadoop Map/Reduce Issue Type:

[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=13185805#comment-13185805 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3656: Glad you ran

[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=13185808#comment-13185808 ] Hadoop QA commented on MAPREDUCE-3656: -- +1 overall. Here are the results of

[jira] [Created] (MAPREDUCE-3669) Getting a lot of PriviledgedActionException / SaslException when running a job

Getting a lot of PriviledgedActionException / SaslException when running a job -- Key: MAPREDUCE-3669 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3669 Project:

[jira] [Commented] (MAPREDUCE-3668) AccessControlException when running mapred job -list command

[ https://issues.apache.org/jira/browse/MAPREDUCE-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185828#comment-13185828 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3668: A quick fix

[jira] [Assigned] (MAPREDUCE-3669) Getting a lot of PriviledgedActionException / SaslException when running a job

[ https://issues.apache.org/jira/browse/MAPREDUCE-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned MAPREDUCE-3669: -- Assignee: Mahadev konar Mahadev, can you please look at

[jira] [Updated] (MAPREDUCE-3628) DFSIO read throughput is decreased by 16% in 0.23 than Hadoop-0.20.204 on 350 nodes size cluster.

[ https://issues.apache.org/jira/browse/MAPREDUCE-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3628: --- Issue Type: Sub-task (was: Task) Parent: MAPREDUCE-3561

[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=13185850#comment-13185850 ] Siddharth Seth commented on MAPREDUCE-3596: --- +1. Patch looks good. Also ran

[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=13185852#comment-13185852 ] Siddharth Seth commented on MAPREDUCE-3656: --- Ran sort again with this patch

[jira] [Updated] (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:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3596: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was:

[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=13185868#comment-13185868 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Hdfs-0.23-Commit #363 (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=13185869#comment-13185869 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Hdfs-trunk-Commit #1612

[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=13185870#comment-13185870 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Common-trunk-Commit #1539

[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=13185872#comment-13185872 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Common-0.23-Commit #373

[jira] [Commented] (MAPREDUCE-3669) Getting a lot of PriviledgedActionException / SaslException when running a job

[ https://issues.apache.org/jira/browse/MAPREDUCE-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185871#comment-13185871 ] Mahadev konar commented on MAPREDUCE-3669: -- Ok, I think I figured out what

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3656: --- Resolution: Fixed Release Note: Fixed a race condition in

[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=13185881#comment-13185881 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Mapreduce-0.23-Commit #385

[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=13185884#comment-13185884 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Hdfs-0.23-Commit #364 (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=13185886#comment-13185886 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Common-trunk-Commit #1540

[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=13185885#comment-13185885 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Common-0.23-Commit #374

[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=13185887#comment-13185887 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Hdfs-trunk-Commit #1613

[jira] [Assigned] (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:all-tabpanel ] Vinod Kumar Vavilapalli reassigned MAPREDUCE-3532: -- Assignee: Bhallamudi Venkata Siva Kamesh When 0 is

[jira] [Commented] (MAPREDUCE-3614) finalState UNDEFINED if AM is killed by hand

[ https://issues.apache.org/jira/browse/MAPREDUCE-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185893#comment-13185893 ] Siddharth Seth commented on MAPREDUCE-3614: --- For the job history related

[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=13185900#comment-13185900 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Mapreduce-0.23-Commit #386

[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=13185901#comment-13185901 ] Hudson commented on MAPREDUCE-3596: --- Integrated in Hadoop-Mapreduce-trunk-Commit

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3532: --- Fix Version/s: 0.23.1 Status: Open (was: Patch

[jira] [Resolved] (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:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-3532. Resolution: Fixed Release Note: Modified NM to report

[jira] [Created] (MAPREDUCE-3670) TaskAttemptListener should respond with errors to unregistered tasks

TaskAttemptListener should respond with errors to unregistered tasks Key: MAPREDUCE-3670 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3670 Project: Hadoop Map/Reduce

[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=13185928#comment-13185928 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Common-trunk-Commit #1541

[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=13185927#comment-13185927 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Common-0.23-Commit #375

[jira] [Created] (MAPREDUCE-3671) AM-NM RPC calls occasionally takes a long time to respond

AM-NM RPC calls occasionally takes a long time to respond - Key: MAPREDUCE-3671 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3671 Project: Hadoop Map/Reduce Issue Type: Bug

[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=13185931#comment-13185931 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Hdfs-0.23-Commit #365 (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=13185932#comment-13185932 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Hdfs-trunk-Commit #1614

[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=13185938#comment-13185938 ] Hudson commented on MAPREDUCE-3656: --- Integrated in Hadoop-Mapreduce-trunk-Commit

[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=13185945#comment-13185945 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Mapreduce-0.23-Commit #387

[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=13185979#comment-13185979 ] Hudson commented on MAPREDUCE-3532: --- Integrated in Hadoop-Mapreduce-trunk-Commit

[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=13185986#comment-13185986 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3404: bq. How do we

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3404: --- Resolution: Fixed Fix Version/s: (was: 0.23.0)

[jira] [Updated] (MAPREDUCE-3672) Killed maps shouldn't be counted towards JobCounter.NUM_FAILED_MAPS

[ https://issues.apache.org/jira/browse/MAPREDUCE-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3672: --- Description: We count maps that are killed, say by speculator,

[jira] [Created] (MAPREDUCE-3672) Killed maps shouldn't be counted towards JobCounter.NUM_FAILED_MAPS

Killed maps shouldn't be counted towards JobCounter.NUM_FAILED_MAPS --- Key: MAPREDUCE-3672 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3672 Project: Hadoop Map/Reduce

[jira] [Commented] (MAPREDUCE-3671) AM-NM RPC calls occasionally takes a long time to respond

[ https://issues.apache.org/jira/browse/MAPREDUCE-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185993#comment-13185993 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3671: .. And this

[jira] [Updated] (MAPREDUCE-3671) AM-NM RPC calls occasionally takes a long time to respond

[ https://issues.apache.org/jira/browse/MAPREDUCE-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3671: --- Issue Type: Sub-task (was: Bug) Parent: MAPREDUCE-3561

[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=13185996#comment-13185996 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Hdfs-0.23-Commit #366 (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=13185997#comment-13185997 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Hdfs-trunk-Commit #1615

[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=13185999#comment-13185999 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Common-trunk-Commit #1542

[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=13186011#comment-13186011 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Mapreduce-0.23-Commit #388

[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=13186024#comment-13186024 ] Hudson commented on MAPREDUCE-3404: --- Integrated in Hadoop-Mapreduce-trunk-Commit