Peng Zhang created MAPREDUCE-6329:
-
Summary: Failure of start map task on NM cause job hang
Key: MAPREDUCE-6329
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6329
Project: Hadoop Map/Reduce
Suppose we configure maven-compiler-plugin with set to 1.7 but
set to 1.8 in trunk. I believe this would have the effect of
generating JDK 8 bytecode, but enforcing that our code sticks to JDK 7
compatibility at compile time. Does that still satisfy requirements for
HADOOP-11858?
I'd prefer to
A few options:
* Only change the builds for master to use jdk8
* build with both jdk7 and jdk8 by copying jobs
* build with both jdk7 and jdk8 using a jenkins matrix build
Robert, if you'd like help with any of these please send me a ping off-list.
On Tue, Apr 21, 2015 at 8:19 PM, Vinod Kumar Va
Brahma Reddy Battula created MAPREDUCE-6328:
---
Summary: NPE in TaskAttemptContextImpl.java
Key: MAPREDUCE-6328
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6328
Project: Hadoop Map/Red
We don't want JDK 8 only code going into branch-2 line. Moving Jenkins to 1.8
right-away will shield such code, how do we address that?
Thanks,
+Vinod
On Apr 21, 2015, at 5:54 PM, Robert Kanter wrote:
> Sure, I'll try to change the Jenkins builds to 1.8 first.
>
> On Tue, Apr 21, 2015 at 3:31
Sure, I'll try to change the Jenkins builds to 1.8 first.
On Tue, Apr 21, 2015 at 3:31 PM, Andrew Wang
wrote:
> Hey Robert,
>
> As a first step, could we try switching all our precommit and nightly
> builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe
> to do in any case si
Sure, I agree it's better to have clear guidelines and scheme. Let me fork this
thread about that.
Re 2.7.0, I just forgot about the naming initially though I was clear in the
discussion/voting. I so had to end up calling it alpha outside of the release
artifact naming.
Thanks
+Vinod
On Apr
Thanks for your comment Karthik. Here's my take.
Feature based release is going to put us back into the same prolonged release
cycle. That is why I am proposing that we look at 2-3 months time and get
whatever is ready. If we don't have even a single feature in by then, clearly
we can drop the
[
https://issues.apache.org/jira/browse/MAPREDUCE-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen resolved MAPREDUCE-6327.
Resolution: Fixed
Fix Version/s: 2.8.0
Hadoop Flags: Reviewed
Committed the
I would also like to support Karthik's proposal on the release thread about
version numbering. 2.7.0 being "alpha" is pretty confusing since all of the
other 2.x releases since GA have been stable. I think users would prefer a
version like "2.8.0-alpha1" instead, which is very clear and similar to
Wangda Tan created MAPREDUCE-6326:
-
Summary: Cleanup ResourceManagerAdministrationProtocol interface
audience
Key: MAPREDUCE-6326
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6326
Project: Had
Hey Robert,
As a first step, could we try switching all our precommit and nightly
builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe
to do in any case since it'll still target 1.7.
I'll note that HADOOP-10530 details the pain Steve went through switching
us to JDK7. Might b
+ yarn-dev, hdfs-dev, mapred-dev
On Tue, Apr 21, 2015 at 3:14 PM, Robert Kanter wrote:
> Hi all,
>
> Moving forward on some of the discussions on Hadoop 3, I've created
> HADOOP-11858 to set the minimum version of Hadoop 3 to JDK 8. I just
> wanted to let everyone know in case there's some reas
The feature set here seems pretty long, even for 2 - 3 months. Can we come
up with a minimum set of features (or a number of features) that justify a
new minor release, and start stabilizing as soon as those are in?
On Tue, Apr 21, 2015 at 2:39 PM, Vinod Kumar Vavilapalli wrote:
> With 2.7.0 out
FYI, MAPREDUCE-6324 is the first JIRA to be tested with the new code in place
if someone hasn’t seen the new output.
On Apr 21, 2015, at 9:06 PM, Allen Wittenauer wrote:
>
>
> Just a heads up that I’ll be committing this to trunk and branch-2 here
> in a bit. I’ll watch it over the n
With 2.7.0 out of the way, and with more maintenance releases to stabilize
it, I propose we start thinking about 2.8.0.
Here's my first cut of the proposal, will update the Roadmap wiki.
- Support *both* JDK7 and JDK8 runtimes: HADOOP-11090
- Compatibility tools to catch backwards, forwards comp
Just a heads up that I’ll be committing this to trunk and branch-2 here
in a bit. I’ll watch it over the next hour or two before heading off to bed.
(I’m in London at the moment.) If there are any issues, revert and drop a note
in HADOOP-11746 with any issues.
Despite what will hope
Harsh J created MAPREDUCE-6325:
--
Summary: Support use of ephemeral client ports for shuffle/etc.
Key: MAPREDUCE-6325
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6325
Project: Hadoop Map/Reduce
Jason Lowe created MAPREDUCE-6324:
-
Summary: Uber jobs fail to update AMRM token when it rolls over
Key: MAPREDUCE-6324
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6324
Project: Hadoop Map/Red
Laurent Goujon created MAPREDUCE-6323:
-
Summary: Support pass-by-reference for ChainMapper/ChainReducer
Key: MAPREDUCE-6323
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6323
Project: Hadoop
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/171/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 10874 lines...]
Failed tests:
TestCombineFi
21 matches
Mail list logo
