[jira] [Created] (MAPREDUCE-3929) output of mapred -showacl is not clear
output of mapred -showacl is not clear -- Key: MAPREDUCE-3929 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3929 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.24.0, 0.23.2, 0.23.3 Reporter: John George Assignee: John George output of 'mapred queue -showacls' is not very clear. This JIRA is aimed at either fixing that or adding something to the document to make it clear. -- 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-3896) pig job through oozie hangs
pig job through oozie hangs Key: MAPREDUCE-3896 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3896 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.1, 0.24.0, 0.23.2 Reporter: John George Assignee: Mahadev konar Priority: Blocker running pig job on oozie hangs due to race condition -- 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-3861) Oozie job status couldn't be updated correctly after Pig job SUCCEEDED from hadoop.
Oozie job status couldn't be updated correctly after Pig job SUCCEEDED from hadoop. --- Key: MAPREDUCE-3861 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3861 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.1, 0.23.2 Reporter: John George Priority: Blocker Submit an Oozie job having Pig action, the job is SUCCEEDED from hadoop and the output file is generated on HDFS, but oozie status is KILLED. Marcy Chen reported this issue while testing a pig job through oozie. -- 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-3758) NPE while submitting job through Oozie
NPE while submitting job through Oozie -- Key: MAPREDUCE-3758 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3758 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.1 Reporter: John George Assignee: John George Priority: Blocker NPE while submitting job through oozie. Caused by: java.lang.NullPointerException at org.apache.hadoop.mapreduce.v2.util.MRApps.setMRFrameworkClasspath(MRApps.java:212) at -- 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-3696) MR job via oozie does not work on hadoop 23
MR job via oozie does not work on hadoop 23 --- Key: MAPREDUCE-3696 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3696 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.1 Reporter: John George Assignee: John George Priority: Critical NM throws an error on submitting an MR job via oozie on the latest Hadoop 23. -- 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-3697) Hadoop Counters API limits Oozie's working across different hadoop versions
Hadoop Counters API limits Oozie's working across different hadoop versions --- Key: MAPREDUCE-3697 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3697 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.1 Reporter: John George Oozie uses Hadoop Counters API, by invoking Counters.getGroup(). However, in hadoop 23, org.apache.hadoop.mapred.Counters does not implement getGroup(). Its parent class AbstractCounters implements it. This is different from hadoop20X. As a result, Oozie compiled with either hadoop version does not work with the other version. A specific scenario, Oozie compiled with .23 and run against 205, does not update job status owing to a Counters API exception. Will explicit re-compilation against the relevant hadoop jars be required each time? This will prevent launching a uniform Oozie version across different clusters. -- 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-3467) Mavenizing har
Mavenizing har -- Key: MAPREDUCE-3467 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3467 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.1 Reporter: John George Priority: Critical As part of mapreduce mavenization, har should also be mavenized and added to maven repo -- 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-3459) ant build is broken in branch-23
ant build is broken in branch-23
Key: MAPREDUCE-3459
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3459
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: John George
ant build is broken in 0.23. A small snippet:
[javac] Compiling 330 source files to
/home//hadoop/branch-0.23/hadoop-mapreduce-project/build/test/mapred/classes
[javac]
/home//hadoop/branch-0.23/hadoop-mapreduce-project/src/test/mapred/org/apache/hadoop/mapred/NotificationTestCase.java:28:
cannot find symbol
[javac] symbol : class MapReduceTestUtil
[javac] location: package org.apache.hadoop.mapreduce
[javac] import org.apache.hadoop.mapreduce.MapReduceTestUtil;
[javac] ^
[javac]
/home//hadoop/branch-0.23/hadoop-mapreduce-project/src/test/mapred/org/apache/hadoop/mapred/TestBadRecords.java:43:
cannot find symbol
[javac] symbol: class ClusterMapReduceTestCase
[javac] public class TestBadRecords extends ClusterMapReduceTestCase {
[javac] ^
--
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-3418) If map output is not found, shuffle runs in tight loop
If map output is not found, shuffle runs in tight loop -- Key: MAPREDUCE-3418 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3418 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.0 Reporter: John George Sharad Agarwal bumped into this while simulating fetch failures. Removed the map output directory. Shuffle runs in tight loop throwing : 2011-06-01 09:02:20,511 WARN org.apache.hadoop.mapreduce.task.reduce.Fetcher: Invalid map id java.lang.IllegalArgumentException: TaskAttemptId string : TTP/1.1 500 Internal Server Error Content-Type: text/plain; charset=UTF is not properly formed at org.apache.hadoop.mapreduce.TaskAttemptID.forName(TaskAttemptID.java:174) at org.apache.hadoop.mapreduce.task.reduce.Fetcher.copyMapOutput(Fetcher.java:284) at org.apache.hadoop.mapreduce.task.reduce.Fetcher.copyFromHost(Fetcher.java:251) at org.apache.hadoop.mapreduce.task.reduce.Fetcher.run(Fetcher.java:149) Fetch failure is not triggered. -- 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-3392) Cluster.getDelegationToken() throws NPE if client.getDelegationToken() returns null.
Cluster.getDelegationToken() throws NPE if client.getDelegationToken() returns null. Key: MAPREDUCE-3392 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3392 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.0, 0.24.0 Reporter: John George Assignee: John George Priority: Blocker Caused by: java.lang.NullPointerException at org.apache.hadoop.mapreduce.Cluster.getDelegationToken(Cluster.java:399) at org.apache.hadoop.mapred.JobClient.getDelegationToken(JobClient.java:1074) at org.apache.oozie.service.KerberosHadoopAccessorService.createJobClient(KerberosHadoopAccessorService.java:139) at org.apache.oozie.action.hadoop.JavaActionExecutor.createJobClient(JavaActionExecutor.java:810) at org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:551) -- 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-3390) NPE while submitting job
NPE while submitting job Key: MAPREDUCE-3390 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3390 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.0, 0.24.0 Reporter: John George Assignee: John George Priority: Blocker Caused by: java.lang.NullPointerException at java.io.Reader.init(Reader.java:61) at java.io.InputStreamReader.init(InputStreamReader.java:55) at org.apache.hadoop.mapreduce.v2.util.MRApps.setMRFrameworkClasspath(MRApps.java:183) at org.apache.hadoop.mapreduce.v2.util.MRApps.setClasspath(MRApps.java:220) at org.apache.hadoop.mapred.YARNRunner.createApplicationSubmissionContext(YARNRunner.java:360) at org.apache.hadoop.mapred.YARNRunner.submitJob(YARNRunner.java:237) at org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:377) at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1159) at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1156) at java.security.AccessController.doPrivileged(Native Method)at javax.security.auth.Subject.doAs(Subject.java:396) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1152) at org.apache.hadoop.mapreduce.Job.submit(Job.java:1156) at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:571) -- 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-3149) add a test to verify that buildDTAuthority works for cases with no authority.
add a test to verify that buildDTAuthority works for cases with no authority. - Key: MAPREDUCE-3149 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3149 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.24.0 Reporter: John George Assignee: John George Add a test to verify that buildDTAuthority works for cases with no Authority. -- 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-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 Versions: 0.23.0, 0.24.0 Reporter: John George Assignee: John George Attachments: mapreduce-3095.patch fairscheduler ivy.xml includes the common version for hdfs dependency. This could break builds that have different common and hdfs version numbers. The reason we dont see it on the jenkins build is because we use the same version number for common and hdfs. -- 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
