[jira] [Commented] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]

[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114493#comment-13114493 ] chackaravarthy commented on MAPREDUCE-3020: --- MAPREDUCE-3009 issue exists for

[jira] [Created] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

Change MR AM to use ApplicationAttemptId rather than everywhere --- Key: MAPREDUCE-3090 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3090 Project: Hadoop

[jira] [Commented] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]

[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114498#comment-13114498 ] Hadoop QA commented on MAPREDUCE-3020: -- -1 overall. Here are the results of test

[jira] [Updated] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-3090: - Status: Patch Available (was: Open) > Change MR AM to use ApplicationAttemptId rathe

[jira] [Updated] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-3090: - Attachment: MAPREDUCE-3090.patch Straight-fwd patch. > Change MR AM to use Applicati

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114505#comment-13114505 ] Venu Gopala Rao commented on MAPREDUCE-3064: Just took a clean workspace a

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114522#comment-13114522 ] Hadoop QA commented on MAPREDUCE-3090: -- +1 overall. Here are the results of test

[jira] [Commented] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]

[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114527#comment-13114527 ] chackaravarthy commented on MAPREDUCE-3020: --- This is trivial change. In Job

[jira] [Updated] (MAPREDUCE-207) Computing Input Splits on the MR Cluster

[ https://issues.apache.org/jira/browse/MAPREDUCE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-207: Attachment: MAPREDUCE-207.patch As foretold, here is a trivial, preliminary patch to mov

[jira] [Updated] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-3090: - Resolution: Fixed Status: Resolved (was: Patch Available) I just committed t

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114537#comment-13114537 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Common-trunk-Commit #954 (

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114539#comment-13114539 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Hdfs-trunk-Commit #1032 (S

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114543#comment-13114543 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Mapreduce-trunk-Commit #97

[jira] [Commented] (MAPREDUCE-2861) Modify version_control.html to reflect new path to mapreduce trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114559#comment-13114559 ] Devaraj K commented on MAPREDUCE-2861: -- It can be closed since it is already upda

[jira] [Created] (MAPREDUCE-3091) "Health-Report" column of NodePage should display more information.

"Health-Report" column of NodePage should display more information. --- Key: MAPREDUCE-3091 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3091 Project: Hadoop Map/Reduce

[jira] [Updated] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated MAPREDUCE-2984: - Attachment: MAPREDUCE-2984-1.patch > Throwing NullPointerException when we open the container

[jira] [Updated] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated MAPREDUCE-2984: - Status: Patch Available (was: Open) Updated the message as per Arun suggestion. > Throwing

[jira] [Commented] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114598#comment-13114598 ] Hadoop QA commented on MAPREDUCE-2984: -- -1 overall. Here are the results of test

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114632#comment-13114632 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Hdfs-trunk #812 (See [htt

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114635#comment-13114635 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Hdfs-0.23-Build #21 (See

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114633#comment-13114633 ] Hudson commented on MAPREDUCE-3064: --- Integrated in Hadoop-Hdfs-trunk #812 (See [htt

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114636#comment-13114636 ] Hudson commented on MAPREDUCE-3064: --- Integrated in Hadoop-Hdfs-0.23-Build #21 (See

[jira] [Commented] (MAPREDUCE-2952) Application failure diagnostics are not consumed in a couple of cases

[ https://issues.apache.org/jira/browse/MAPREDUCE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114634#comment-13114634 ] Hudson commented on MAPREDUCE-2952: --- Integrated in Hadoop-Hdfs-trunk #812 (See [htt

[jira] [Commented] (MAPREDUCE-2952) Application failure diagnostics are not consumed in a couple of cases

[ https://issues.apache.org/jira/browse/MAPREDUCE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114637#comment-13114637 ] Hudson commented on MAPREDUCE-2952: --- Integrated in Hadoop-Hdfs-0.23-Build #21 (See

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114643#comment-13114643 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Mapreduce-0.23-Build #27 (

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114644#comment-13114644 ] Hudson commented on MAPREDUCE-3064: --- Integrated in Hadoop-Mapreduce-0.23-Build #27 (

[jira] [Commented] (MAPREDUCE-3090) Change MR AM to use ApplicationAttemptId rather than everywhere

[ https://issues.apache.org/jira/browse/MAPREDUCE-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114650#comment-13114650 ] Hudson commented on MAPREDUCE-3090: --- Integrated in Hadoop-Mapreduce-trunk #842 (See

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114651#comment-13114651 ] Hudson commented on MAPREDUCE-3064: --- Integrated in Hadoop-Mapreduce-trunk #842 (See

[jira] [Commented] (MAPREDUCE-2952) Application failure diagnostics are not consumed in a couple of cases

[ https://issues.apache.org/jira/browse/MAPREDUCE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114652#comment-13114652 ] Hudson commented on MAPREDUCE-2952: --- Integrated in Hadoop-Mapreduce-trunk #842 (See

[jira] [Updated] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

[ https://issues.apache.org/jira/browse/MAPREDUCE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-2646: --- Component/s: applicationmaster Affects Version/s: 0.23.0

[jira] [Commented] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

[ https://issues.apache.org/jira/browse/MAPREDUCE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114654#comment-13114654 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-2646: We need to wr

[jira] [Assigned] (MAPREDUCE-3089) Re-enable TestRMContainerAllocator

[ https://issues.apache.org/jira/browse/MAPREDUCE-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned MAPREDUCE-3089: -- Assignee: Vinod Kumar Vavilapalli We need to add a test for

[jira] [Updated] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

[ https://issues.apache.org/jira/browse/MAPREDUCE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-2646: --- Resolution: Fixed Status: Resolved (was: Patch Available)

[jira] [Commented] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

[ https://issues.apache.org/jira/browse/MAPREDUCE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114664#comment-13114664 ] Hudson commented on MAPREDUCE-2646: --- Integrated in Hadoop-Common-trunk-Commit #955 (

[jira] [Commented] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

[ https://issues.apache.org/jira/browse/MAPREDUCE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114665#comment-13114665 ] Hudson commented on MAPREDUCE-2646: --- Integrated in Hadoop-Hdfs-trunk-Commit #1033 (S

[jira] [Commented] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

[ https://issues.apache.org/jira/browse/MAPREDUCE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114670#comment-13114670 ] Hudson commented on MAPREDUCE-2646: --- Integrated in Hadoop-Mapreduce-trunk-Commit #97

[jira] [Commented] (MAPREDUCE-3050) YarnScheduler needs to expose Resource Usage Information

[ https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114679#comment-13114679 ] Eric Payne commented on MAPREDUCE-3050: --- @Bobby, Would it be possible to change

[jira] [Reopened] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened MAPREDUCE-3064: This patch broke the ant build for MRV1, I cannot compile a test. (

[jira] [Resolved] (MAPREDUCE-2861) Modify version_control.html to reflect new path to mapreduce trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-2861. Resolution: Invalid Someone fixed this. Not valid anymore. > M

[jira] [Resolved] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-3064. Resolution: Fixed Never mind, ran into the stale jars issue. >

[jira] [Updated] (MAPREDUCE-3050) YarnScheduler needs to expose Resource Usage Information

[ https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated MAPREDUCE-3050: --- Target Version/s: 0.23.0, 0.24.0 (was: 0.24.0, 0.23.0) Stat

[jira] [Updated] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3054: --- Status: Open (was: Patch Available) Looked at the patch. Some qu

[jira] [Created] (MAPREDUCE-3092) Remove JOB_ID_COMPARATOR usage in JobHistory.java

Remove JOB_ID_COMPARATOR usage in JobHistory.java - Key: MAPREDUCE-3092 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3092 Project: Hadoop Map/Reduce Issue Type: Bug Components

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114711#comment-13114711 ] Venu Gopala Rao commented on MAPREDUCE-3064: Vinod, any idea why Jenkins i

[jira] [Commented] (MAPREDUCE-3064) 27 unit test failures with Invalid "mapreduce.jobtracker.address" configuration value for JobTracker: "local"

[ https://issues.apache.org/jira/browse/MAPREDUCE-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114712#comment-13114712 ] Mahadev konar commented on MAPREDUCE-3064: -- @venu, Jenkins is running into s

[jira] [Commented] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114720#comment-13114720 ] Mahadev konar commented on MAPREDUCE-3054: -- I think most of the client comman

[jira] [Created] (MAPREDUCE-3093) Write tests for data locality in MRv2.

Write tests for data locality in MRv2. -- Key: MAPREDUCE-3093 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3093 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.0 R

[jira] [Updated] (MAPREDUCE-3093) Write additional tests for data locality in MRv2.

[ https://issues.apache.org/jira/browse/MAPREDUCE-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated MAPREDUCE-3093: - Summary: Write additional tests for data locality in MRv2. (was: Write tests for dat

[jira] [Updated] (MAPREDUCE-2843) [MR-279] Node entries on the RM UI are not sortable

[ https://issues.apache.org/jira/browse/MAPREDUCE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhijit Suresh Shingate updated MAPREDUCE-2843: --- Attachment: (was: MAPREDUCE-2843.2.patch) > [MR-279] Node ent

[jira] [Updated] (MAPREDUCE-2843) [MR-279] Node entries on the RM UI are not sortable

[ https://issues.apache.org/jira/browse/MAPREDUCE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhijit Suresh Shingate updated MAPREDUCE-2843: --- Attachment: MAPREDUCE-2843.2.patch > [MR-279] Node entries on the

[jira] [Updated] (MAPREDUCE-2843) [MR-279] Node entries on the RM UI are not sortable

[ https://issues.apache.org/jira/browse/MAPREDUCE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhijit Suresh Shingate updated MAPREDUCE-2843: --- Attachment: MAPREDUCE-2843.2.patch > [MR-279] Node entries on the

[jira] [Commented] (MAPREDUCE-2843) [MR-279] Node entries on the RM UI are not sortable

[ https://issues.apache.org/jira/browse/MAPREDUCE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114750#comment-13114750 ] Abhijit Suresh Shingate commented on MAPREDUCE-2843: Hi Lu, Thanks

[jira] [Commented] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114749#comment-13114749 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3054: That's a litt

[jira] [Commented] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114754#comment-13114754 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3054: bq. Also jobs

[jira] [Commented] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114759#comment-13114759 ] Mahadev konar commented on MAPREDUCE-3054: -- @Vinod, Its probably not differe

[jira] [Commented] (MAPREDUCE-2843) [MR-279] Node entries on the RM UI are not sortable

[ https://issues.apache.org/jira/browse/MAPREDUCE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114764#comment-13114764 ] Luke Lu commented on MAPREDUCE-2843: Why is a custom writer/validator necessary? I

[jira] [Created] (MAPREDUCE-3094) org.apache.hadoop.streaming.TestUlimit.testCommandLine fails intermittantly in 20.205.0

org.apache.hadoop.streaming.TestUlimit.testCommandLine fails intermittantly in 20.205.0 --- Key: MAPREDUCE-3094 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3094

[jira] [Commented] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114801#comment-13114801 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3054: bq. I dont th

[jira] [Commented] (MAPREDUCE-3031) Job Client goes into infinite loop when we kill AM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114820#comment-13114820 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3031: +1, lgtm. Th

[jira] [Updated] (MAPREDUCE-3031) Job Client goes into infinite loop when we kill AM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3031: --- Resolution: Fixed Hadoop Flags: [Reviewed] Status:

[jira] [Commented] (MAPREDUCE-3084) race when KILL_CONTAINER is received for a LOCALIZED container

[ https://issues.apache.org/jira/browse/MAPREDUCE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114830#comment-13114830 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3084: Good catch, S

[jira] [Commented] (MAPREDUCE-3031) Job Client goes into infinite loop when we kill AM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114832#comment-13114832 ] Hudson commented on MAPREDUCE-3031: --- Integrated in Hadoop-Hdfs-trunk-Commit #1034 (S

[jira] [Commented] (MAPREDUCE-3031) Job Client goes into infinite loop when we kill AM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114831#comment-13114831 ] Hudson commented on MAPREDUCE-3031: --- Integrated in Hadoop-Common-trunk-Commit #956 (

[jira] [Updated] (MAPREDUCE-3050) YarnScheduler needs to expose Resource Usage Information

[ https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated MAPREDUCE-3050: --- Attachment: MR-3050.txt Uploading a new patch. I upmerged and changed ge

[jira] [Updated] (MAPREDUCE-3050) YarnScheduler needs to expose Resource Usage Information

[ https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated MAPREDUCE-3050: --- Target Version/s: 0.23.0, 0.24.0 (was: 0.24.0, 0.23.0) Stat

[jira] [Commented] (MAPREDUCE-3031) Job Client goes into infinite loop when we kill AM

[ https://issues.apache.org/jira/browse/MAPREDUCE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114845#comment-13114845 ] Hudson commented on MAPREDUCE-3031: --- Integrated in Hadoop-Mapreduce-trunk-Commit #97

[jira] [Updated] (MAPREDUCE-3056) Jobs are failing when those are submitted by other users

[ https://issues.apache.org/jira/browse/MAPREDUCE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3056: --- Component/s: applicationmaster Fix Version/s: 0.23.0 I ran

RE: [jira] [Updated] (MAPREDUCE-3056) Jobs are failing when those are submitted by other users

Hi Vinod, I faced the problem exaclty as you explained. The problem is the default staging dir use of ${user.name} system property, which is the job-submitter on the client side and the system user on the server side. I started working on this issue, I will submit patch soon. Thanks

[jira] [Updated] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated MAPREDUCE-3095: --- Target Version/s: 0.23.0, 0.24.0 > fairscheduler ivy including wrong version for hdfs

[jira] [Updated] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated MAPREDUCE-3095: --- Attachment: mapreduce-3095.patch > fairscheduler ivy including wrong version for hdfs

[jira] [Created] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

fairscheduler ivy including wrong version for hdfs -- Key: MAPREDUCE-3095 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3095 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versio

[jira] [Updated] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated MAPREDUCE-3095: --- Target Version/s: 0.23.0, 0.24.0 (was: 0.24.0, 0.23.0) Tags: mr2 mrv2

[jira] [Updated] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated MAPREDUCE-3095: --- Attachment: mapreduce-branch-0.23.patch attaching the same patch for branch 23.

[jira] [Updated] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated MAPREDUCE-3095: --- Component/s: mrv2 Target Version/s: 0.23.0, 0.24.0 (was: 0.24.0, 0.23.0)

[jira] [Created] (MAPREDUCE-3096) Add a good way to control the number of map/reduce tasks per node

Add a good way to control the number of map/reduce tasks per node - Key: MAPREDUCE-3096 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3096 Project: Hadoop Map/Reduce Issu

[jira] [Updated] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-2984: - Priority: Minor (was: Major) Affects Version/s: (was: 0.24.0)

[jira] [Updated] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-2984: - Resolution: Fixed Status: Resolved (was: Patch Available) I just committed t

[jira] [Commented] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114913#comment-13114913 ] Mahadev konar commented on MAPREDUCE-3095: -- +1 looks good to me. Nice catch J

[jira] [Updated] (MAPREDUCE-3095) fairscheduler ivy including wrong version for hdfs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated MAPREDUCE-3095: - Target Version/s: 0.23.0, 0.24.0 (was: 0.24.0, 0.23.0) Affects Version/s: (w

[jira] [Commented] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114915#comment-13114915 ] Hudson commented on MAPREDUCE-2984: --- Integrated in Hadoop-Common-trunk-Commit #957 (

[jira] [Commented] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114916#comment-13114916 ] Hudson commented on MAPREDUCE-2984: --- Integrated in Hadoop-Hdfs-trunk-Commit #1035 (S

[jira] [Created] (MAPREDUCE-3097) archive does not archive if the content specified is a file

archive does not archive if the content specified is a file --- Key: MAPREDUCE-3097 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3097 Project: Hadoop Map/Reduce Issue Type: Bug

[jira] [Commented] (MAPREDUCE-3097) archive does not archive if the content specified is a file

[ https://issues.apache.org/jira/browse/MAPREDUCE-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114921#comment-13114921 ] Arpit Gupta commented on MAPREDUCE-3097: archive command was issued as such b

[jira] [Commented] (MAPREDUCE-2984) Throwing NullPointerException when we open the container page

[ https://issues.apache.org/jira/browse/MAPREDUCE-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114923#comment-13114923 ] Hudson commented on MAPREDUCE-2984: --- Integrated in Hadoop-Mapreduce-trunk-Commit #97

[jira] [Commented] (MAPREDUCE-3056) Jobs are failing when those are submitted by other users

[ https://issues.apache.org/jira/browse/MAPREDUCE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114932#comment-13114932 ] Aaron T. Myers commented on MAPREDUCE-3056: --- FWIW, basically the same bug ex

[jira] [Commented] (MAPREDUCE-3088) Clover 2.4.3 breaks build for 0.22 branch

[ https://issues.apache.org/jira/browse/MAPREDUCE-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114937#comment-13114937 ] Konstantin Boudnik commented on MAPREDUCE-3088: --- I don't see any problem

[jira] [Assigned] (MAPREDUCE-3088) Clover 2.4.3 breaks build for 0.22 branch

[ https://issues.apache.org/jira/browse/MAPREDUCE-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik reassigned MAPREDUCE-3088: - Assignee: Konstantin Shvachko > Clover 2.4.3 breaks build for 0.2

[jira] [Commented] (MAPREDUCE-2764) Fix renewal of dfs delegation tokens

[ https://issues.apache.org/jira/browse/MAPREDUCE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114946#comment-13114946 ] Daryn Sharp commented on MAPREDUCE-2764: Is there an estimate for when this ji

[jira] [Updated] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated MAPREDUCE-3067: --- Attachment: MR-3067.1.patch Trivial fix with modified unit tests. > Con

[jira] [Updated] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated MAPREDUCE-3067: --- Status: Patch Available (was: Open) > Container exit status not set properly to laun

[jira] [Assigned] (MAPREDUCE-3098) Report Application status as well as ApplicationMaster status in GetApplicationReportResponse

[ https://issues.apache.org/jira/browse/MAPREDUCE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah reassigned MAPREDUCE-3098: -- Assignee: Hitesh Shah > Report Application status as well as ApplicationMaster

[jira] [Updated] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated MAPREDUCE-3067: --- Status: Open (was: Patch Available) Minor copy-paste fix pending > Cont

[jira] [Created] (MAPREDUCE-3098) Report Application status as well as ApplicationMaster status in GetApplicationReportResponse

Report Application status as well as ApplicationMaster status in GetApplicationReportResponse -- Key: MAPREDUCE-3098 URL: https://issues.apache.org/jira/browse/MAPREDUCE-

[jira] [Commented] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114971#comment-13114971 ] Hadoop QA commented on MAPREDUCE-3067: -- +1 overall. Here are the results of test

[jira] [Updated] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated MAPREDUCE-3067: --- Attachment: MR-3067.2.patch Fixed error in LCE tests. > Container exit

[jira] [Updated] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated MAPREDUCE-3067: --- Status: Patch Available (was: Open) > Container exit status not set properly to laun

[jira] [Updated] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated MAPREDUCE-3054: - Attachment: MAPREDUCE-3054.patch Ok, here's a compromise. We cant change the job api'

[jira] [Updated] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated MAPREDUCE-3054: - Status: Patch Available (was: Open) > Unable to kill submitted jobs > --

[jira] [Updated] (MAPREDUCE-3054) Unable to kill submitted jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated MAPREDUCE-3054: - Status: Open (was: Patch Available) Fixing javadoc. For the test failure, it looks l

[jira] [Commented] (MAPREDUCE-3067) Container exit status not set properly to launched process's exit code on successful completion of process

[ https://issues.apache.org/jira/browse/MAPREDUCE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115009#comment-13115009 ] Hadoop QA commented on MAPREDUCE-3067: -- +1 overall. Here are the results of test

  1   2   >