[jira] [Resolved] (MAPREDUCE-5319) Job.xml file does not has 'user.name' property for Hadoop2
[ https://issues.apache.org/jira/browse/MAPREDUCE-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved MAPREDUCE-5319. -- Resolution: Fixed I just committed this. Thanks [~xgong]! Job.xml file does not has 'user.name' property for Hadoop2 -- Key: MAPREDUCE-5319 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5319 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 2.1.0-beta Reporter: yeshavora Assignee: Xuan Gong Fix For: 2.1.0-beta Attachments: MR-5319.2.patch, MR-5319.patch Run a sleep job and look for job.xml file generated by sleep job. It does not contain user.name property. -- 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] [Resolved] (MAPREDUCE-3533) have the service interface extend Closeable and use close() as its shutdown operation
[
https://issues.apache.org/jira/browse/MAPREDUCE-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved MAPREDUCE-3533.
---
Resolution: Fixed
Fix Version/s: 2.1.0-beta
Fixed in the YARN-530 patch. {{close()}} forwards to {{stop()}}
have the service interface extend Closeable and use close() as its shutdown
operation
-
Key: MAPREDUCE-3533
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3533
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: mrv2
Affects Versions: 0.23.0, 0.23.1, 0.24.0
Reporter: Steve Loughran
Priority: Minor
Fix For: 2.1.0-beta
This is probably going be marked down as a wontfix on the basis that it is
(almost) encoded in the interfaces, but it may not be too late.
If the service interface interface extended Closeable and used close()
instead of stop(), it would work automatically in the java7 automatic
resource management blocks...
--
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
Hadoop-Mapreduce-trunk - Build # 1457 - Failure
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1457/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 30280 lines...] Running org.apache.hadoop.mapreduce.TestChild Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.542 sec Running org.apache.hadoop.mapreduce.filecache.TestURIFragments Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec Running org.apache.hadoop.mapreduce.TestMapReduce Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.745 sec Results : Tests run: 463, Failures: 0, Errors: 0, Skipped: 11 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-mapreduce-client ... SUCCESS [1.647s] [INFO] hadoop-mapreduce-client-core .. SUCCESS [35.408s] [INFO] hadoop-mapreduce-client-common SUCCESS [23.716s] [INFO] hadoop-mapreduce-client-shuffle ... SUCCESS [2.262s] [INFO] hadoop-mapreduce-client-app ... SUCCESS [5:31.905s] [INFO] hadoop-mapreduce-client-hs SUCCESS [1:23.119s] [INFO] hadoop-mapreduce-client-jobclient . FAILURE [43:53.539s] [INFO] hadoop-mapreduce-client-hs-plugins SKIPPED [INFO] Apache Hadoop MapReduce Examples .. SKIPPED [INFO] hadoop-mapreduce .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 51:52.239s [INFO] Finished at: Fri Jun 14 14:07:52 UTC 2013 [INFO] Final Memory: 19M/138M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on project hadoop-mapreduce-client-jobclient: ExecutionException; nested exception is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hadoop-mapreduce-client-jobclient Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE Archiving artifacts Updating MAPREDUCE-4019 Updating MAPREDUCE-5199 Updating YARN-117 Updating HDFS-4845 Updating YARN-746 Updating YARN-792 Updating YARN-773 Updating YARN-812 Updating MAPREDUCE-5319 Updating YARN-692 Updating HDFS-4902 Updating MAPREDUCE-5298 Updating YARN-530 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
Visual debugging tools for hadoop
Hi Folks, I was wondering if anyone is currently working on or thinking about visual debugging tools for mapreduce jobs, I was thinking about starting an effort to build an end to end visual tool that shows all the steps in the mapreduce workflow and data flows, variable content changing to speed up debugging of jobs.Please ignore if something like this already exists and if not I'd love to collaborate with folks to build something. Regards
Re: Visual debugging tools for hadoop
Hi Saikat, You might want to investigate contributing on Apache Ambari, which has features for visualization of jobs and end-to-end flows consisting of multiple dependent jobs. http://incubator.apache.org/ambari/ Chris Nauroth Hortonworks http://hortonworks.com/ On Fri, Jun 14, 2013 at 8:20 AM, Saikat Kanjilal sxk1...@hotmail.comwrote: Hi Folks, I was wondering if anyone is currently working on or thinking about visual debugging tools for mapreduce jobs, I was thinking about starting an effort to build an end to end visual tool that shows all the steps in the mapreduce workflow and data flows, variable content changing to speed up debugging of jobs.Please ignore if something like this already exists and if not I'd love to collaborate with folks to build something. Regards
Re: Heads up: branch-2.1-beta
As Ramya noted, things are looking good on branch-2.1-beta ATM. Henceforth, can I please ask committers to hold off non-blocker fixes for the final set of tests? thanks, Arun On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote: Folks, The vast majority of of the planned features and API work is complete, thanks to everyone who contributed! I've created a branch-2.1-beta branch from which I anticipate I can make the first of our beta releases very shortly. For now the remaining work is to wrap up loose ends i.e. last minute api work (e.g. YARN-759 showed up last night for consideration), bug-fixes etc.; then run this through a battery of unit/system/integration tests and do a final review before we ship. There is more work remaining on documentation (e.g. HADOOP-9517) and I plan to personally focus on it this week - obviously help reviewing docs is very welcome. Committers, from now, please please exercise your judgement on where you commit. Typically, features should go into branch-2 with 2.3.0 as the version on jira (fix-version 2.3.0 is ready). The expectation is that 2.2.0 will be limited to content in branch-2.1-beta and we stick to stabilizing it henceforth (I've deliberately not created 2.2.0 fix-version on jira yet). thanks, Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
Re: Heads up: branch-2.1-beta
Arun, This sounds great. Following is the list of JIRAs I'd like to get in. Note that the are ready or almost ready, my estimate is that they can be taken care of in a couple of day. Thanks. * YARN-752: In AMRMClient, automatically add corresponding rack requests for requested nodes impact: behavior change status: patch avail, reviewed by Bikas. As Bikas did some changes it needs another committer to look at it. * YARN-521: Augment AM - RM client module to be able to request containers only at specific locations impact: AMRM client API change status: patch avail, needs to be reviewed, needs YARN-752 * YARN-791: Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API impact: Yarn client API proto change status: patch avail, review in progress * YARN-649: Make container logs available over HTTP in plain text impact: Addition to NM HTTP REST API. Needed for MAPREDUCE-4362 (which does not change API) status: patch avail, review in progress * MAPREDUCE-5171: Expose blacklisted nodes from the MR AM REST API impact: Addition to MRAM HTTP API status: patch avail, +1ed, needs to be committed * MAPREDUCE-5130: Add missing job config options to mapred-default.xml impact: behavior change status: patch avail, needs to be reviewed * MAPREDUCE-5311: Remove slot millis computation logic and deprecate counter constants impact: behavior change status: patch avail, needs to be reviewed * YARN-787: Remove resource min from Yarn client API impact: Yarn client API change status: patch needs rebase, depends on MAPREDUCE-5311 On Fri, Jun 14, 2013 at 1:17 PM, Arun C Murthy a...@hortonworks.com wrote: As Ramya noted, things are looking good on branch-2.1-beta ATM. Henceforth, can I please ask committers to hold off non-blocker fixes for the final set of tests? thanks, Arun On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote: Folks, The vast majority of of the planned features and API work is complete, thanks to everyone who contributed! I've created a branch-2.1-beta branch from which I anticipate I can make the first of our beta releases very shortly. For now the remaining work is to wrap up loose ends i.e. last minute api work (e.g. YARN-759 showed up last night for consideration), bug-fixes etc.; then run this through a battery of unit/system/integration tests and do a final review before we ship. There is more work remaining on documentation (e.g. HADOOP-9517) and I plan to personally focus on it this week - obviously help reviewing docs is very welcome. Committers, from now, please please exercise your judgement on where you commit. Typically, features should go into branch-2 with 2.3.0 as the version on jira (fix-version 2.3.0 is ready). The expectation is that 2.2.0 will be limited to content in branch-2.1-beta and we stick to stabilizing it henceforth (I've deliberately not created 2.2.0 fix-version on jira yet). thanks, Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- Alejandro
[jira] [Created] (MAPREDUCE-5323) Min Spills For Combine Ignored
Jeff Bean created MAPREDUCE-5323:
Summary: Min Spills For Combine Ignored
Key: MAPREDUCE-5323
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5323
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: task
Reporter: Jeff Bean
Priority: Minor
We've observed for some time that combiners always run when specified. However
there is a config called mapreduce.map.combine.minspills which sort of implies
that the developer or administrator ought to be able to control when combiners
are invoked.
I spelunked into the code and found this gem in MapTask.java:
if (combinerRunner == null || numSpills minSpillsForCombine) {
Merger.writeFile(kvIter, writer, reporter, job); } else {
combineCollector.setWriter(writer); combinerRunner.combine(kvIter,
combineCollector); }
That looks way buggy to me. If ( A || B ) is made false by A then B is never
executed. I spelunked around the code some more and it looks like
combinerRunner is never null except on reflection failure. So it looks like the
intention is for minSpillsForCombine to be respected, but due to this logic
error it's totally ignored.
--
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-5324) Admin-provided user environment can be overridden by user provided values for the AM
Hitesh Shah created MAPREDUCE-5324: -- Summary: Admin-provided user environment can be overridden by user provided values for the AM Key: MAPREDUCE-5324 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5324 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Hitesh Shah Priority: Minor MRJobConfig.MR_AM_ADMIN_USER_ENV can be overridden by MRJobConfig.MR_AM_ENV. Either the variable should be renamed to something along the lines of DEFAULT_ENV or the code fixed to have the correct overrides. Current documentation clearly states user env overrides admin env. -- 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] [Resolved] (MAPREDUCE-4942) mapreduce.Job has a bunch of methods that throw InterruptedException so its incompatible with MR1
[
https://issues.apache.org/jira/browse/MAPREDUCE-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen resolved MAPREDUCE-4942.
Resolution: Fixed
Close the ticket. Actually, these methods are binary compatible with both MRv1
and 0.23. However, due to the conflicting method signature (throwing or not
throwing InterruptedException), these methods are source incompatible either
with MRv1 or 0.23.
Again, it is better be compatible with MRv1, as it has larger user base, while
0.23 users don't need much change to fix the code. Assume that a MRv1
application is not binary compatible because of mapreduce.Counter, whose binary
incompatibility will not be fixed. The user can recompile the code against MRv2
jars, and recompilation will not fail at mapreduce.Job given this ticket fixed.
Will document this imcompatible change in MAPREDUCE-5184 as well.
mapreduce.Job has a bunch of methods that throw InterruptedException so its
incompatible with MR1
-
Key: MAPREDUCE-4942
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4942
Project: Hadoop Map/Reduce
Issue Type: Sub-task
Components: mrv2
Affects Versions: 2.0.2-alpha
Reporter: Robert Kanter
Assignee: Robert Kanter
Fix For: 2.1.0-beta
Attachments: MAPREDUCE-4942.patch
The following methods in MR2's {{org.apache.hadoop.mapreduce.Job}} throw an
{{InterruptedException}} but don't in MR1, which makes them incompatible.
(Their Javadoc comments are also missing that they throw an
{{InterruptedException}} anyway)
I propose that we wrap the {{InterruptedException}} in a
{{RuntimeException}}.
{code}
public float setupProgress() throws IOException, InterruptedException
public float mapProgress() throws IOException, InterruptedException
public float reduceProgress() throws IOException, InterruptedException
public boolean isComplete() throws IOException, InterruptedException
public boolean isSuccessful() throws IOException, InterruptedException
public void killJob() throws IOException, InterruptedException
public void killTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
IOException, InterruptedException
public void failTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
IOException, InterruptedException
public Counters getCounters() throws IOException, InterruptedException
{code}
--
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
Re: Heads up: branch-2.1-beta
Arun Forgot to make it explicit in previous email, I'll be happy to help so this is done ASAP. Please, let me know how you want to proceed Thx On Fri, Jun 14, 2013 at 2:02 PM, Alejandro Abdelnur t...@cloudera.comwrote: Arun, This sounds great. Following is the list of JIRAs I'd like to get in. Note that the are ready or almost ready, my estimate is that they can be taken care of in a couple of day. Thanks. * YARN-752: In AMRMClient, automatically add corresponding rack requests for requested nodes impact: behavior change status: patch avail, reviewed by Bikas. As Bikas did some changes it needs another committer to look at it. * YARN-521: Augment AM - RM client module to be able to request containers only at specific locations impact: AMRM client API change status: patch avail, needs to be reviewed, needs YARN-752 * YARN-791: Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API impact: Yarn client API proto change status: patch avail, review in progress * YARN-649: Make container logs available over HTTP in plain text impact: Addition to NM HTTP REST API. Needed for MAPREDUCE-4362 (which does not change API) status: patch avail, review in progress * MAPREDUCE-5171: Expose blacklisted nodes from the MR AM REST API impact: Addition to MRAM HTTP API status: patch avail, +1ed, needs to be committed * MAPREDUCE-5130: Add missing job config options to mapred-default.xml impact: behavior change status: patch avail, needs to be reviewed * MAPREDUCE-5311: Remove slot millis computation logic and deprecate counter constants impact: behavior change status: patch avail, needs to be reviewed * YARN-787: Remove resource min from Yarn client API impact: Yarn client API change status: patch needs rebase, depends on MAPREDUCE-5311 On Fri, Jun 14, 2013 at 1:17 PM, Arun C Murthy a...@hortonworks.comwrote: As Ramya noted, things are looking good on branch-2.1-beta ATM. Henceforth, can I please ask committers to hold off non-blocker fixes for the final set of tests? thanks, Arun On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote: Folks, The vast majority of of the planned features and API work is complete, thanks to everyone who contributed! I've created a branch-2.1-beta branch from which I anticipate I can make the first of our beta releases very shortly. For now the remaining work is to wrap up loose ends i.e. last minute api work (e.g. YARN-759 showed up last night for consideration), bug-fixes etc.; then run this through a battery of unit/system/integration tests and do a final review before we ship. There is more work remaining on documentation (e.g. HADOOP-9517) and I plan to personally focus on it this week - obviously help reviewing docs is very welcome. Committers, from now, please please exercise your judgement on where you commit. Typically, features should go into branch-2 with 2.3.0 as the version on jira (fix-version 2.3.0 is ready). The expectation is that 2.2.0 will be limited to content in branch-2.1-beta and we stick to stabilizing it henceforth (I've deliberately not created 2.2.0 fix-version on jira yet). thanks, Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- Alejandro -- Alejandro
[jira] [Resolved] (MAPREDUCE-5323) Min Spills For Combine Ignored
[
https://issues.apache.org/jira/browse/MAPREDUCE-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Bean resolved MAPREDUCE-5323.
--
Resolution: Not A Problem
Misunderstood config mapreduce.map.combine.minspills as the number of spills to
require before the first combine. Instead, it's the number of spills required
for a second and subsequent combines on merge.
Min Spills For Combine Ignored
--
Key: MAPREDUCE-5323
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5323
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: task
Reporter: Jeff Bean
Priority: Minor
We've observed for some time that combiners always run when specified.
However there is a config called mapreduce.map.combine.minspills which sort
of implies that the developer or administrator ought to be able to control
when combiners are invoked.
I spelunked into the code and found this gem in MapTask.java:
if (combinerRunner == null || numSpills minSpillsForCombine) {
Merger.writeFile(kvIter, writer, reporter, job); } else {
combineCollector.setWriter(writer); combinerRunner.combine(kvIter,
combineCollector); }
That looks way buggy to me. If ( A || B ) is made false by A then B is never
executed. I spelunked around the code some more and it looks like
combinerRunner is never null except on reflection failure. So it looks like
the intention is for minSpillsForCombine to be respected, but due to this
logic error it's totally ignored.
--
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] [Resolved] (MAPREDUCE-5275) Mapreduce API: TokenCache incompatibility issues with MR1
[ https://issues.apache.org/jira/browse/MAPREDUCE-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved MAPREDUCE-5275. Resolution: Fixed CacheToken is the class that provides user facing APIs. Whether the methods as annotated private or not, users are likely to refer them in their custom routines, because they are public. We fixed MAPREDUCE-5220 for the similar reason. IMHO, it is good to keep the rule of binary compatibility consistent. In addition, adding the methods back does no harm to MRv2 if they are actually not used. Feel free to reopen it, if you still have some concern. Thanks! Mapreduce API: TokenCache incompatibility issues with MR1 - Key: MAPREDUCE-5275 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5275 Project: Hadoop Map/Reduce Issue Type: Sub-task Reporter: Zhijie Shen Assignee: Mayank Bansal Fix For: 2.1.0-beta Attachments: MAPREDUCE-5275-trunk-1.patch, MAPREDUCE-5275-trunk-2.patch, MAPREDUCE-5275-trunk-3.patch, MAPREDUCE-5275-trunk-4.patch There're following incompatibility issues: * TokenDelegationTokenIdentifier getDelegationToken(Credentials, String) is removed * Credentials loadTokens(String, Configuration) changes to Credentials loadTokens(String, JobConf) -- 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-5325) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter---MR changes
Xuan Gong created MAPREDUCE-5325: Summary: ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter---MR changes Key: MAPREDUCE-5325 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5325 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Xuan Gong Assignee: Xuan Gong -- 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
Re: Heads up: branch-2.1-beta
On Thu, Jun 6, 2013 at 4:48 AM, Arun C Murthy a...@hortonworks.com wrote: On Jun 5, 2013, at 11:04 AM, Roman Shaposhnik wrote On the Bigtop side of things, once we have stable Bigtop 0.6.0 platform based on Hadoop 2.0.x codeline we plan to start running the same battery of integration tests on the branch-2.1-beta. We plan to simply file JIRAs if anything gets detected and I will also publish the URL of the Jenkins job once it gets created. Thanks Roman. Is there an ETA for this? Also, please file jiras with Blocker priority to catch attention. The build is up and running (and all green on all of the 9 Linux platforms!): http://bigtop01.cloudera.org:8080/job/Hadoop-2.1.0/ The immediate benefit here is that we get to see that the build is ok on all these Linuxes and all anybody can easily install packaged Hadoop 2.1.0 nightly builds. Starting from next week, I'll start running regular tests on these bits and will keep you guys posted! Thanks, Roman.
Re: Heads up: branch-2.1-beta
Following is a revisited assessment of JIRAs I would like to get in the 2.1 release: From the 1st group I think all 3 should make. From the 2nd group I think YARN-791 should make it for sure and ideally MAPREDUCE-5130. From the 3rd group, I don't think this JIRA will make it. From the 4th group, we don't need to worry about this or 2.1 Thanks Alejandro -- JIRAs that are in shape to make it to 2.1 * YARN-752: In AMRMClient, automatically add corresponding rack requests for requested nodes impact: behavior change status: patch avail, +1ed. * MAPREDUCE-5171: Expose blacklisted nodes from the MR AM REST API impact: Addition to MRAM HTTP API status: patch avail, +1ed, needs to be committed * YARN-787: Remove resource min from Yarn client API impact: Yarn client API change status: patch avail, needs to be reviewed. (the calculation of slot-millis is not affected, the MIN is taken from conf for now) -- JIRAs that require minor work to make it to 2.1 * YARN-521: Augment AM - RM client module to be able to request containers only at specific locations impact: AMRM client API change status: patch not avail yet (requires YARN-752) * YARN-791: Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API impact: Yarn client API proto change status: patch avail, review in progress * MAPREDUCE-5130: Add missing job config options to mapred-default.xml impact: behavior change status: patch avail but some tests are failing -- JIRAs that require significant work to make it to 2.1 and may not make it * YARN-649: Make container logs available over HTTP in plain text impact: Addition to NM HTTP REST API. Needed for MAPREDUCE-4362 (which does not change API) status: patch avail, review in progress -- JIRAs that don't need to make it to 2.1 * MAPREDUCE-5311: Remove slot millis computation logic and deprecate counter constants impact: behavior change status: per discussion we should first add memory-millis and vcores-millis -- On Fri, Jun 14, 2013 at 7:17 PM, Roman Shaposhnik r...@apache.org wrote: On Thu, Jun 6, 2013 at 4:48 AM, Arun C Murthy a...@hortonworks.com wrote: On Jun 5, 2013, at 11:04 AM, Roman Shaposhnik wrote On the Bigtop side of things, once we have stable Bigtop 0.6.0 platform based on Hadoop 2.0.x codeline we plan to start running the same battery of integration tests on the branch-2.1-beta. We plan to simply file JIRAs if anything gets detected and I will also publish the URL of the Jenkins job once it gets created. Thanks Roman. Is there an ETA for this? Also, please file jiras with Blocker priority to catch attention. The build is up and running (and all green on all of the 9 Linux platforms!): http://bigtop01.cloudera.org:8080/job/Hadoop-2.1.0/ The immediate benefit here is that we get to see that the build is ok on all these Linuxes and all anybody can easily install packaged Hadoop 2.1.0 nightly builds. Starting from next week, I'll start running regular tests on these bits and will keep you guys posted! Thanks, Roman. -- Alejandro
