If there are not a lot of changes just to make Java 7 a requirement (I
understand it's basically pom changes and unit test failure and findbugs
fallouts), how about merging that with the next release and declare the
next release and on Java-7-only?
On Mon, Dec 8, 2014 at 3:02 PM, Steve Loughran
w
On 8 December 2014 at 19:48, Colin McCabe wrote:
> Are there a lot of open JDK7
> issues that would require a release to straighten out?
>
I don't think so —the 2.6 release was tested pretty aggressively on JDK7,
and solely on it for Windows. Pushing out a 2.7 release would be more
symbolic than
On Fri, Dec 5, 2014 at 11:15 AM, Karthik Kambatla wrote:
> It would be nice to cut the branch for the next "feature" release (not just
> Java 7) in the first week of January, so we can get the RC out by the end
> of the month?
>
> Yesterday, this came up in an offline discussion on ATS. Given peop
It would be nice to cut the branch for the next "feature" release (not just
Java 7) in the first week of January, so we can get the RC out by the end
of the month?
Yesterday, this came up in an offline discussion on ATS. Given people can
run 2.6 on Java 7, is there merit to doing 2.7 with the exac
Late January sounds fine to me. I think we should be able to wrap it up
much earlier than that (hopefully).
Thanks,
Sangjin
On Tue, Dec 2, 2014 at 5:19 PM, Arun C Murthy wrote:
> Sangjin/Karthik,
>
> How about planning on hadoop-2.8 by late Jan? Thoughts?
>
> thanks,
> Arun
>
> On Dec 2, 2014,
Sangjin/Karthik,
How about planning on hadoop-2.8 by late Jan? Thoughts?
thanks,
Arun
On Dec 2, 2014, at 11:09 AM, Sangjin Lee wrote:
> If 2.7 is being positioned as the JDK7-only release, then it would be good
> to know how 2.8 lines up in terms of timing. Our interest is landing the
> share
If 2.7 is being positioned as the JDK7-only release, then it would be good
to know how 2.8 lines up in terms of timing. Our interest is landing the
shared cache feature (YARN-1492)... Thanks.
Sangjin
On Mon, Dec 1, 2014 at 2:55 PM, Karthik Kambatla wrote:
> Thanks for starting this thread, Arun
Thanks for starting this thread, Arun.
Your proposal seems reasonable to me. I suppose we would like new features
and improvements to go into 2.8 then? If yes, what time frame are we
looking at for 2.8? Looking at YARN, it would be nice to get a release with
shared-cache and a stable version of re
Folks,
With hadoop-2.6 out it's time to think ahead.
As we've discussed in the past, 2.6 was the last release which supports JDK6.
I'm thinking it's best to try get 2.7 out in a few weeks (maybe by the
holidays) with just the switch to JDK7 (HADOOP-10530) and possibly
support for JDK-1.8 (as a r
>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I actually would like to see both archival storage and single replica
>>>>>>>> memory writes to be in 2.6 release. Archival storage is in the
t;>>>> in the final stages to be merged to branch-2.
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>> Tsz-Wo
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>&g
00 AM, Suresh Srinivas <
> >>>>>> sur...@hortonworks.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> I actually would like to see b
rks.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> I actually would like to see both archival storage and single
> replica
> >>>>>>
gt;>>>> memory writes to be in 2.6 release. Archival storage is in the final
>>>>>> stages
>>>>>>> of getting ready for branch-2 merge as Nicholas has already indicated
>>>> on
>>>>>>> the dev mailing list. Hopefully HDFS-
; stages
>>>>>>> of getting ready for branch-2 merge as Nicholas has already indicated
>>>> on
>>>>>>> the dev mailing list. Hopefully HDFS-6581 gets ready sooner. Both of
>>>>> these
>>>>>>> features are bei
ngly?
>>>>>>
>>>>>> I think the KMS and transparent encryption are ready to go. We've
>> got
>>> a
>>>>>> very few further bug fixes pending, but that's it.
>>>>>>
>>>>>> Two
eds a little more work before it goes into
> > branch-2.
> > > >> HDFS-6581 hasn't even been merged to trunk yet, so seems a bit
> further
> > > off
> > > >> yet.
> > > >>
> > > >&g
it - hopefully in the next few weeks.
>
> Thoughts?
>
> thanks,
> Arun
>
> On Tue, Aug 12, 2014 at 1:34 PM, Arun C Murthy
> wrote:
>
> > Folks,
> >
> > With hadoop-2.5 nearly done, it's time to start thinking ahead to
> > hadoop-
nt encryption are ready to go. We've
> > got
> > > a
> > > > >> very few further bug fixes pending, but that's it.
> > > > >>
> > > > >> Two HDFS things that I think probably won't make the end of the
> week
> > > ar
ingle replica memory writes
> > > (HDFS-6581),
> > > >> which I believe are under the HSM banner. HDFS-6484 was just merged
> to
> > > >> trunk and I think needs a little more work before it goes into
> > branch-2.
> > > >> HDFS-6581 hasn'
work directly on these features. I just
> > generally
> > >> shy away from shipping bits quite this fresh.
> > >>
> > >> Thanks,
> > >> Andrew
> > >>
> > >> On Tue, Sep 23, 2014 at 3:03 PM,
t;> Andrew
> >>
> >> On Tue, Sep 23, 2014 at 3:03 PM, Arun Murthy
> wrote:
> >>
> >> > Looks like most of the content is in and hadoop-2.6 is shaping up
> nicely.
> >> >
> >> > I'll create branch-2.6 by end of the week
n Tue, Sep 23, 2014 at 3:03 PM, Arun Murthy wrote:
>>
>> > Looks like most of the content is in and hadoop-2.6 is shaping up nicely.
>> >
>> > I'll create branch-2.6 by end of the week and we can go from there to
>> > stabilize it - hopefully in the n
did not work directly on these features. I just
> > > generally
> > > > > shy away from shipping bits quite this fresh.
> > > > >
> > > > > Thanks,
> > > > > Andrew
> > > > >
> > > > > On Tue, Sep 2
t; > generally
> > > > shy away from shipping bits quite this fresh.
> > > >
> > > > Thanks,
> > > > Andrew
> > > >
> > > > On Tue, Sep 23, 2014 at 3:03 PM, Arun Murthy
> > > wrote:
> > > >
> > &g
he content is in and hadoop-2.6 is shaping up
> > nicely.
> > > >
> > > > I'll create branch-2.6 by end of the week and we can go from there to
> > > > stabilize it - hopefully in the next few weeks.
> > > >
> > > > Thoughts?
&g
; >
> > > Looks like most of the content is in and hadoop-2.6 is shaping up
> nicely.
> > >
> > > I'll create branch-2.6 by end of the week and we can go from there to
> > > stabilize it - hopefully in the next few weeks.
> > >
> > >
run Murthy
> wrote:
> >
> > > Looks like most of the content is in and hadoop-2.6 is shaping up
> nicely.
> > >
> > > I'll create branch-2.6 by end of the week and we can go from there to
> > > stabilize it - hopefully in the next few weeks.
> &g
to
> > stabilize it - hopefully in the next few weeks.
> >
> > Thoughts?
> >
> > thanks,
> > Arun
> >
> > On Tue, Aug 12, 2014 at 1:34 PM, Arun C Murthy
> > wrote:
> >
> > > Folks,
> > >
> > > With hadoop-2.5
;
> I'll create branch-2.6 by end of the week and we can go from there to
> stabilize it - hopefully in the next few weeks.
>
> Thoughts?
>
> thanks,
> Arun
>
> On Tue, Aug 12, 2014 at 1:34 PM, Arun C Murthy
> wrote:
>
> > Folks,
> >
> >
gt;
> With hadoop-2.5 nearly done, it's time to start thinking ahead to
> hadoop-2.6.
>
> Currently, here is the Roadmap per the wiki:
>
> • HADOOP
> • Credential provider HADOOP-10607
> • HDFS
> • Heterogeneous storage (
Sorry, coming to discussion late.
We all agreed that 2.6 would the *last* release supporting JDK6 and
hadoop-2.7 would drop support for JDK6. We could easily do 2.7 right after
2.6 (maybe with few critical bug-fixes) with the defining feature of 2.7
being *JDK7 only*. I've checked with HBase, Pig
There's actually an umbrella JIRA to track issues with JDK8
(HADOOP-11090), in case anyone missed it.
At LinkedIn we've been running our Hadoop 2.3 deployment on JDK8 for
about a month now with some mixed results. It definitely works but
there are issues, mostly around virtual memory exploding.
On Sep 17, 2014, at 2:47 AM, Steve Loughran wrote:
>
> I don't agree. Certainly the stuff I got into Hadoop 2.5 nailed down the
> filesystem binding with more tests than ever before.
FWIW, based upon my survey of JIRA, there are a lot of unit test fixes
that are only in trunk.
> But
gt; to
> > the list? We have most of the patches for the sub-JIRAs under review and
> > have committed a couple.
> >
> > -Subru
> >
> > -- Forwarded message --
> >
> > From: Arun C Murthy
> >
> > Date: Tue, Aug 12, 2014 a
On Sep 15, 2014, at 11:17 AM, Colin McCabe wrote:
> On Mon, Sep 15, 2014 at 10:48 AM, Allen Wittenauer wrote:
>>
>>It’s now September. With the passage of time, I have a lot of doubts
>> about this plan and where that trajectory takes us.
>>
>> * The list of changes that are already
e patches for the sub-JIRAs under review and
>> have committed a couple.
>>
>> -Subru
>>
>> -- Forwarded message --
>>
>> From: Arun C Murthy
>>
>> Date: Tue, Aug 12, 2014 at 1:34 PM
>>
>> Subject: Thinking ahead to ha
he sub-JIRAs under review and
> have committed a couple.
>
> -Subru
>
> -- Forwarded message --
>
> From: Arun C Murthy
>
> Date: Tue, Aug 12, 2014 at 1:34 PM
>
> Subject: Thinking ahead to hadoop-2.6
>
> To: "common-dev@hadoop
e, Aug 12, 2014 at 1:34 PM
Subject: Thinking ahead to hadoop-2.6
To: "common-dev@hadoop.apache.org" , "
hdfs-...@hadoop.apache.org" , "
mapreduce-...@hadoop.apache.org" ,
"yarn-...@hadoop.apache.org"
Folks,
With hadoop-2.5 nearly done, i
Folks,
With hadoop-2.5 nearly done, it's time to start thinking ahead to hadoop-2.6.
Currently, here is the Roadmap per the wiki:
• HADOOP
• Credential provider HADOOP-10607
• HDFS
• Heterogeneous storage (Phase 2) - Support APIs for
Hi,
+1 for 2.4.1 release(non-binding).
There are some critical issues including YARN-1861 and YARN-1929 about
RM-HA. IMO, we should include the fixes.
One question is whether we can include RM-HA phase 2(YARN-556) in 2.5
by mid-May. It's still work-in-progress.
Thanks,
- Tsuyoshi
On Mon, Apr 1
+1 (non-binding) for 2.4.1 release.
> We can debate whether or June is too early for hadoop-2.5 and it's
> contents, but I recollect there was consensus that releases every 6
> weeks (or so) makes sense.
Also, +1 (non-binding) for the 6 weeks (or so) timeline releases.
However, I'm thinking it's
On Sun, Apr 13, 2014 at 5:50 PM, Arun C Murthy wrote:
>
> I just opened https://issues.apache.org/jira/browse/YARN-1935.
I've just assigned the ticket to me, and opened/linked a number of related
tickets. I'll work on the security issues of the timeline server.
Thanks,
Zhijie
--
Zhijie Shen
H
Reference:
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3ccajs6+b4tkupvqfaorf_314xveivryqy-vtryd8+36tu_bc5...@mail.gmail.com%3E
This is of course open source, and I have neither the ability nor the
desire to compel or pressure anybody to work on anything, but I wanted to
Unfortunately I don't have the bandwidth to take on ATS security at this
time. My (I now understand mistaken) impression that it was being worked
on, as we had discussed it under the initial criteria for including the AHS
in a release. I brought it up as a feature I felt worth waiting for if it
m
Sandy,
On Apr 12, 2014, at 10:09 AM, Sandy Ryza wrote:
> I'm having trouble editing the wiki, but I think Timeline Server stability
> (e.g. security and locking down APIs) should go on that list.
I'm very glad to see you are very passionate about security for ATS since
you've asked about it
I'm still wading through 2.4.1 critical issues (failing tests, blockers
etc) so haven't gotten time to think about the 2.5 list w.r.t YARN. Will do
so in the next week.
BTW, folks, please refrain from adding items to the list that you
yourselves are not volunteering to work on. Anyone keen to see
> On Apr 12, 2014, at 10:09 AM, Sandy Ryza wrote:
>
> +1 for starting to think about 2.5. Early June seems a little early to me
> - we had talked about a quarterly release cadence and this would be about
> half that.
We can debate whether or June is too early for hadoop-2.5 and it's contents,
+1 for Timeline Server stability. In addition to the security, we may also
want to deal with scalability, generic and per-framework services
integration and MR integration.
Any plan about YARN long running services?
On Sat, Apr 12, 2014 at 10:09 AM, Sandy Ryza wrote:
> +1 for starting to think
+1 for starting to think about 2.5. Early June seems a little early to me
- we had talked about a quarterly release cadence and this would be about
half that.
I'm having trouble editing the wiki, but I think Timeline Server stability
(e.g. security and locking down APIs) should go on that list.
+1
The proposed content for 2.5 in the roadmap wiki looks good to me.
On Apr 12, 2014 7:26 AM, "Arun C Murthy" wrote:
> Gang,
>
> With hadoop-2.4 out, it's time to think ahead.
>
> In the short-term hadoop-2.4.1 is in order; particularly with
> https://issues.apache.org/jira/browse/MAPREDUCE-5
Gang,
With hadoop-2.4 out, it's time to think ahead.
In the short-term hadoop-2.4.1 is in order; particularly with
https://issues.apache.org/jira/browse/MAPREDUCE-5830 (it's a break to @Private
API, unfortunately something Hive is using - sigh!). There are some other fixes
which testing has
mp;
> Support
> >>>>> for Heterogenous Storage.
> >>>>>>
> >>>>>> Now, most of the key pieces incl. Resource Manager Automatic
> Failover
> >>>>> (YARN-149), Application History Server (YARN-321) &
age.
>>>>>>
>>>>>> Now, most of the key pieces incl. Resource Manager Automatic Failover
>>>>> (YARN-149), Application History Server (YARN-321) & Application Timeline
>>>>> Server (YARN-1530) are either complete or very close to d
RN-1530) are either complete or very close to done, and I think
>>>> we will benefit with an extended test-cycle for 2.4 - similar to what
>>>> happened with 2.2. To provide some context: 2.2 went through nearly 6 weeks
>>>> of extended testing and it
me context: 2.2 went through nearly 6 weeks
>>> of extended testing and it really helped us push out a very stable release.
>>>>
>>>> I think it will be good to create a 2.4 branch ASAP and start testing.
>>> As such, I plan to cut the branch early next wee
; of extended testing and it really helped us push out a very stable release.
>>>
>>> I think it will be good to create a 2.4 branch ASAP and start testing.
>> As such, I plan to cut the branch early next week. With this, we should be
>> good shape sometime to rel
it really helped us push out a very stable release.
> >
> > I think it will be good to create a 2.4 branch ASAP and start testing.
> As such, I plan to cut the branch early next week. With this, we should be
> good shape sometime to release 2.4 in mid-March.
> >
> >
very stable release.
>>
>> I think it will be good to create a 2.4 branch ASAP and start testing. As
>> such, I plan to cut the branch early next week. With this, we should be good
>> shape sometime to release 2.4 in mid-March.
>>
>> I've updated https:
> such, I plan to cut the branch early next week. With this, we should be good
> shape sometime to release 2.4 in mid-March.
>
> I've updated https://wiki.apache.org/hadoop/Roadmap to reflect this.
>
> Also, we should start thinking ahead to 2.5 and what folks would like to see
> such, I plan to cut the branch early next week. With this, we should be good
> shape sometime to release 2.4 in mid-March.
>
> I've updated https://wiki.apache.org/hadoop/Roadmap to reflect this.
>
> Also, we should start thinking ahead to 2.5 and what folks would like to see
e 2.4 in mid-March.
I've updated https://wiki.apache.org/hadoop/Roadmap to reflect this.
Also, we should start thinking ahead to 2.5 and what folks would like to see
in it. If we continue our 6-week cycles, we could shoot to get that out in
April.
Thoughts?
thanks,
Arun
--
Arun C. Murth
62 matches
Mail list logo
