Re: mapreduce.jobtracker.address vs. yarn.resourcemanager.address
If I understand correctly from searching for it in the code, while not deprecated, the property currently has no effect. Does that not sound right to you Harsh? Was there a conclusion on: may I deprecate it, or is there a larger decision being waited on? -Sandy On Fri, Feb 8, 2013 at 9:35 PM, Harsh J ha...@cloudera.com wrote: Yes, there isn't a classic version of mapreduce.framework.name now either. Its mostly being used as a pseudonym. MR1 no longer exists in 2.x releases/trunk. Note though that Oozie still relies on that specific property (JT address) and 0.22 clients may also perhaps be using it. We can deprecate it and remove on 3.x or later. On Sat, Feb 9, 2013 at 4:00 AM, Alejandro Abdelnur t...@cloudera.com wrote: MR1 code is already gone from trunk and branch-2 Thx On Fri, Feb 8, 2013 at 2:27 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: There was a time when there were thoughts of being able to run MR1 in parallel with YARN while the later took off. So they were supposed to coexist, hence the non-deprecation. I am not sure we formally did, but once it is cast in stone that MR1 cannot be run with Hadoop 2.0 *(by which time we should remove JT/TT etc.), then we can deprecate these configs. Thanks, +Vinod On Feb 8, 2013, at 2:15 PM, Sandy Ryza wrote: Is there a reason why mapreduce.jobtracker.address is not deprecated to yarn.resourcemanager.address? thanks, Sandy -- Alejandro -- Harsh J
Re: mapreduce.jobtracker.address vs. yarn.resourcemanager.address
Sorry for ambiguity. Yes, we may deprecate now and remove in next major release. On Mon, Feb 11, 2013 at 1:17 AM, Sandy Ryza sandy.r...@cloudera.com wrote: If I understand correctly from searching for it in the code, while not deprecated, the property currently has no effect. Does that not sound right to you Harsh? Was there a conclusion on: may I deprecate it, or is there a larger decision being waited on? -Sandy On Fri, Feb 8, 2013 at 9:35 PM, Harsh J ha...@cloudera.com wrote: Yes, there isn't a classic version of mapreduce.framework.name now either. Its mostly being used as a pseudonym. MR1 no longer exists in 2.x releases/trunk. Note though that Oozie still relies on that specific property (JT address) and 0.22 clients may also perhaps be using it. We can deprecate it and remove on 3.x or later. On Sat, Feb 9, 2013 at 4:00 AM, Alejandro Abdelnur t...@cloudera.com wrote: MR1 code is already gone from trunk and branch-2 Thx On Fri, Feb 8, 2013 at 2:27 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: There was a time when there were thoughts of being able to run MR1 in parallel with YARN while the later took off. So they were supposed to coexist, hence the non-deprecation. I am not sure we formally did, but once it is cast in stone that MR1 cannot be run with Hadoop 2.0 *(by which time we should remove JT/TT etc.), then we can deprecate these configs. Thanks, +Vinod On Feb 8, 2013, at 2:15 PM, Sandy Ryza wrote: Is there a reason why mapreduce.jobtracker.address is not deprecated to yarn.resourcemanager.address? thanks, Sandy -- Alejandro -- Harsh J -- Harsh J
Re: pre-historic record IO stuff, is this used anywhere?
Thanks Harsh, I'll wait a couple more days and if there are no objections I'll prepare a patch to get rid of them. Thx On Fri, Feb 8, 2013 at 9:15 PM, Harsh J ha...@cloudera.com wrote: Hadoop streaming is also tied to recordio as it is today: https://issues.apache.org/jira/browse/MAPREDUCE-3303, but it can be removed per Klaas. On Sat, Feb 9, 2013 at 6:48 AM, Alejandro Abdelnur t...@cloudera.com wrote: This seems to be used only in tests in common and in a standalone class in streaming tests. What is the purpose of these classes as they don't seem to be used in the any of the source that ends up in Hadoop? hadoop-common-project/hadoop-common/src/test/ddl/buffer.jr hadoop-common-project/hadoop-common/src/test/ddl/int.jr hadoop-common-project/hadoop-common/src/test/ddl/string.jr hadoop-common-project/hadoop-common/src/test/ddl/test.jr hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/record/FromCpp.java hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/record/RecordBench.java hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/record/TestBuffer.java hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/record/TestRecordIO.java hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/record/TestRecordVersioning.java hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/record/ToCpp.java hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/typedbytes/TestIO.java I've deleted the above classes, cleaned up the common POM (not to compile the JR files) and everything compiles fine. To me all this is dead code, if so, can we nuke them? Thx -- Alejandro -- Harsh J -- Alejandro
[jira] [Created] (MAPREDUCE-4997) Deprecate mapreduce.jobtracker.address
Sandy Ryza created MAPREDUCE-4997: - Summary: Deprecate mapreduce.jobtracker.address Key: MAPREDUCE-4997 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4997 Project: Hadoop Map/Reduce Issue Type: Improvement Affects Versions: 2.0.2-alpha Reporter: Sandy Ryza Assignee: Sandy Ryza mapreduce.jobtracker.address currently is not used, but users transitioning from mr1 to mr2 may expect their previous job configs to work, so it should be deprecated in favor of yarn.resourcemanager.address. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4998) backport MAPREDUCE-3376: Old mapred API combiner uses NULL reporter to branch-1
Jim Donofrio created MAPREDUCE-4998: --- Summary: backport MAPREDUCE-3376: Old mapred API combiner uses NULL reporter to branch-1 Key: MAPREDUCE-4998 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4998 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv1 Reporter: Jim Donofrio Priority: Minor backport MAPREDUCE-3376: Old mapred API combiner uses NULL reporter to branch-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
