On Mon, Jan 28, 2013 at 03:11PM, Roman Shaposhnik wrote:
> Hi Arun,
>
> On Wed, Jan 16, 2013 at 6:52 AM, Arun C Murthy wrote:
> > Happy new year folks!
> >
> > I'm glad to see that we are down to the last couple of blockers I hope we
> > can resolve in the next 24-hrs or so.
> >
> > Once done, I
On Tue, Jan 29, 2013 at 9:51 AM, Arun C Murthy wrote:
> I believe we can disregard MAPREDUCE-4820 since MAPREDUCE-4549 is already in
> branch-2. FYI.
Arun, that very well may be the case -- let me take a closer look and
report back (on the JIRA).
Also, any chance you could comment on when the b
I believe we can disregard MAPREDUCE-4820 since MAPREDUCE-4549 is already in
branch-2. FYI.
On Jan 29, 2013, at 8:51 AM, Roman Shaposhnik wrote:
> On Mon, Jan 28, 2013 at 3:11 PM, Roman Shaposhnik wrote:
>> Hi Arun,
>>
>> On Wed, Jan 16, 2013 at 6:52 AM, Arun C Murthy wrote:
>>> Happy new yea
+1 - that'd be critical.
On Tue, Jan 29, 2013 at 08:51AM, Roman Shaposhnik wrote:
> On Mon, Jan 28, 2013 at 3:11 PM, Roman Shaposhnik wrote:
> > Hi Arun,
> >
> > On Wed, Jan 16, 2013 at 6:52 AM, Arun C Murthy wrote:
> >> Happy new year folks!
> >>
> >> I'm glad to see that we are down to the las
On Mon, Jan 28, 2013 at 3:11 PM, Roman Shaposhnik wrote:
> Hi Arun,
>
> On Wed, Jan 16, 2013 at 6:52 AM, Arun C Murthy wrote:
>> Happy new year folks!
>>
>> I'm glad to see that we are down to the last couple of blockers I hope we
>> can resolve in the next 24-hrs or so.
>>
>> Once done, I'll cr
Hi Arun,
On Wed, Jan 16, 2013 at 6:52 AM, Arun C Murthy wrote:
> Happy new year folks!
>
> I'm glad to see that we are down to the last couple of blockers I hope we can
> resolve in the next 24-hrs or so.
>
> Once done, I'll create a branch-2.0.3-alpha to unblock branch-2
> for commits targeted
I'd like to get in 2.0.3 the JIRAs that enable pluggable shuffle and
pluggable sort: MAPREDUCE-4049, MAPREDUCE-4809, MAPREDUCE-4807 &
MAPREDUCE-4808
Unless I hear otherwise, I'd be merging those commits in branch-2 tomorrow
mid afternoon PST.
Thx
On Wed, Jan 16, 2013 at 10:38 AM, Arun C Murthy
Seems reasonable since it's a small patch and has had one round of review.
I spoke to Todd yesterday and he seemed to think it can be pushed in fairly
soon too. So that's two of you.
Anyway, since I'm still awaiting HADOOP-9215 too, I'd appreciate if we can get
HDFS-4404 committed asap.
thanks
Arun,
HDFS-4404 is not marked as a blocker. It is a serious bug and I would like
to make it a blocker. Let me know if you are okay.
If folks do not want to hold the release for that fix, lets at least try to
capture that in release notes and try get that fix into 2.0.4.
Regards,
Suresh
On Wed,
Happy new year folks!
I'm glad to see that we are down to the last couple of blockers I hope we can
resolve in the next 24-hrs or so.
Once done, I'll create a branch-2.0.3-alpha to unblock branch-2 for commits
targeted towards the next release, create the new fix-versions in jira and spin
the
Message-
From: Aaron T. Myers [mailto:a...@cloudera.com]
Sent: Tuesday, December 18, 2012 9:07 PM
To: general@hadoop.apache.org
Subject: Re: Heads Up - hadoop-2.0.3 release
Great, that makes sense to me as well.
Thanks a lot, and have a happy holidays.
Aaron
On Tue, Dec 18, 2012 at 9:00 PM, Arun
On 19 December 2012 11:26, Prabakaran Krishnan wrote:
> Hi
> How to insert and update datin hadoop? Could you please explain me...
>
> Thanks
> Prabakara Krishnan
>
>
1. please don't steal ongoing threads for asking questions
2. this is the kind of question to ask on the user@hadoop list. Please
Hi
How to insert and update datin hadoop? Could you please explain me...
Thanks
Prabakara Krishnan
From: Aaron T. Myers
To: general@hadoop.apache.org
Sent: Wednesday, 19 December 2012 10:37 AM
Subject: Re: Heads Up - hadoop-2.0.3 release
Great, that
Great, that makes sense to me as well.
Thanks a lot, and have a happy holidays.
Aaron
On Tue, Dec 18, 2012 at 9:00 PM, Arun C Murthy wrote:
> As Sid responded I think we can move off alpha once we fix
> YARN-142/MAPREDUCE-4067. There are other apis we should clean up, but none
> as egregious
As Sid responded I think we can move off alpha once we fix
YARN-142/MAPREDUCE-4067. There are other apis we should clean up, but none as
egregious as those two.
Someone on my team is starting on it as we speak and I believe we can get it
done sometime in Jan... thus targetting 2.0.4 (as a beta?
Hey Arun,
Awesome to see we're almost down to zero blockers. What are your thoughts
on removing the "alpha" label from the upcoming release? It seems to me
from the earlier discussion that most folks feel that we're at the point
where the interfaces are sufficiently stable to warrant it.
Aaron
Nearly there:
http://s.apache.org/hadoop-2-blockers
YARN-217 should be easy, I'd also like to get in YARN-253.
Arun
On Dec 19, 2012, at 1:15 AM, Todd Lipcon wrote:
> Any news on how this is progressing? Some folks in this thread below
> inquired about getting this release out around the New Yea
Any news on how this is progressing? Some folks in this thread below
inquired about getting this release out around the New Year timeframe,
but it looks like YARN-117 subtasks have gone pretty quiet. We all
know how long lifecycle changes can take to get pushed through ;-)
-Todd
On Mon, Nov 19, 2
Hey Arun,
On Tue, Dec 4, 2012 at 6:09 AM, Arun C Murthy wrote:
> Feel free to watch the blocker list:
> http://s.apache.org/e1J
>
I notice that query doesn't include "2.0.3-alpha" in the "affected
version" or "target version" fields. You should probably add it to get the
complete list of blo
OK, QJM is now in branch-2. I also merged all the follow-up patches I
could find so that branch-2 and trunk should be equivalent with regard
to QJM functionality at this point. If anyone sees anything I missed,
feel free to give me a holler.
Thanks
Todd
On Tue, Dec 4, 2012 at 6:56 PM, Arun Murthy
Thanks Todd!
On Dec 4, 2012, at 6:04 PM, Todd Lipcon wrote:
> Hey Arun,
>
> I put up patches for the QJM backport merge yesterday. Aaron said he'd
> take a look at reviewing them, so I anticipate that to be finished
> "real soon now". Sorry for the delay.
>
> -Todd
>
> On Tue, Dec 4, 2012 at 6:
Hey Arun,
I put up patches for the QJM backport merge yesterday. Aaron said he'd
take a look at reviewing them, so I anticipate that to be finished
"real soon now". Sorry for the delay.
-Todd
On Tue, Dec 4, 2012 at 6:09 AM, Arun C Murthy wrote:
> Lohit,
>
> There are some outstanding blockers
Lohit,
There are some outstanding blockers and I'm still awaiting the QJM merge.
Feel free to watch the blocker list:
http://s.apache.org/e1J
Arun
On Dec 3, 2012, at 10:02 AM, lohit wrote:
> Hello Hadoop Release managers,
> Any update on this?
>
> Thanks,
> Lohit
>
> 2012/11/20 Tom White
On Mon, Dec 3, 2012 at 10:02 AM, lohit wrote:
> Hello Hadoop Release managers,
> Any update on this?
To pile on (and hopefully revive the old thread):
Is there any chance that Hadoop 2.0.3 can
be pushed out before the end of the year?
Also, based on the experience of working on Bigtop 0.5.0
it
Hello Hadoop Release managers,
Any update on this?
Thanks,
Lohit
2012/11/20 Tom White
> On Mon, Nov 19, 2012 at 6:09 PM, Siddharth Seth
> wrote:
> > YARN-142/MAPREDUCE-4067 should ideally be fixed before we commit to API
> > backward compatibility. Also, from the recent YARN meetup - there see
On Mon, Nov 19, 2012 at 6:09 PM, Siddharth Seth
wrote:
> YARN-142/MAPREDUCE-4067 should ideally be fixed before we commit to API
> backward compatibility. Also, from the recent YARN meetup - there seemed to
> be a requirement to change the AM-RM protocol for container requests. In
> this case, I b
+1 for the API changes. We need to be careful about back-compat but at the
same time the API's are the core of YARN and there seem to be some issues
around it.
Bikas
On 11/19/12 10:09 AM, "Siddharth Seth" wrote:
>YARN-142/MAPREDUCE-4067 should ideally be fixed before we commit to API
>backward
I want to make some changes to the lifecycle of a yarn service (in a
backwards compatible way).
https://issues.apache.org/jira/browse/YARN-117
1. formal state machine model with stop state idempotent and entry-able
from any state
2. waiting/blocked state a service can enter when waiting
I want to explicitly point out that the backward compatibility that is
being brought up here is related to APIs alone. I am fine with that as long
as it is for the APIs exposed to the users/applications. Incompatible API
changes, if necessary, among the daemons in Hadoop should be allowed. Also
if
Agreed, I was about to point this out.
What else is on HDFS of this nature?
Arun
On Nov 19, 2012, at 10:09 AM, Siddharth Seth wrote:
> YARN-142/MAPREDUCE-4067 should ideally be fixed before we commit to API
> backward compatibility. Also, from the recent YARN meetup - there seemed to
> be a req
YARN-142/MAPREDUCE-4067 should ideally be fixed before we commit to API
backward compatibility. Also, from the recent YARN meetup - there seemed to
be a requirement to change the AM-RM protocol for container requests. In
this case, I believe it's OK to not have all functionality implemented, as
lon
+1 for MAPREDUCE-2424
Best wishes
- Mensaje original -
De: Mariappan Asokan
Para: general@hadoop.apache.org
Enviado: Mon, 19 Nov 2012 12:18:34 -0500 (EST)
Asunto: Re: Heads Up - hadoop-2.0.3 release
I also agree with Millind and Alejandro.
Thanks.
-- Asokan
Agree with Milind, I&#
I also agree with Millind and Alejandro.
Thanks.
-- Asokan
Agree with Milind, I'd also like to see MAPREDUCE-2454 in it.
Thx
On Fri, Nov 16, 2012 at 4:05 PM, Bhandarkar, Milind
wrote:
> I would recommend https://issues.apache.org/jira/browse/MAPREDUCE-2454 for
> inclusion.
>
> - milind
>
> --
We really need https://issues.apache.org/jira/browse/MAPREDUCE-4805 too.
The history server is completely useless without it.
--Bobby
On 11/16/12 10:27 PM, "Alejandro Abdelnur" wrote:
>Agree with Milind, I'd also like to see MAPREDUCE-2454 in it.
>
>Thx
>
>On Fri, Nov 16, 2012 at 4:05 PM, Bhand
I am OK with removing the alpha assuming that we think that the APIs are
stable enough that we are willing to truly start maintaining backwards
compatibility on them within 2.X. From what I have seen I think that they
are fairly stable and I think there is enough adoption by other projects
right no
On Fri, Nov 16, 2012 at 3:38 PM, Aaron T. Myers wrote:
> Hi Arun,
>
> Given that the 2.0.3 release is intended to reflect the growing stability
> of YARN, and the QJM work will be included in 2.0.3 which provides a
> complete HDFS HA solution, I think it's time we consider removing the
> "-alpha"
Agree with Milind, I'd also like to see MAPREDUCE-2454 in it.
Thx
On Fri, Nov 16, 2012 at 4:05 PM, Bhandarkar, Milind
wrote:
> I would recommend https://issues.apache.org/jira/browse/MAPREDUCE-2454 for
> inclusion.
>
> - milind
>
> ---
> Milind Bhandarkar
> Chief Scientist,
> Machine Learning Pl
I would recommend https://issues.apache.org/jira/browse/MAPREDUCE-2454 for
inclusion.
- milind
---
Milind Bhandarkar
Chief Scientist,
Machine Learning Platforms,
Greenplum, A Division of EMC
+1-650-523-3858 (W)
+1-408-666-8483 (C)
On 11/16/12 3:38 PM, "Aaron T. Myers" wrote:
>Hi Arun,
>
>G
Hi Arun,
Given that the 2.0.3 release is intended to reflect the growing stability
of YARN, and the QJM work will be included in 2.0.3 which provides a
complete HDFS HA solution, I think it's time we consider removing the
"-alpha" label from the release version. My preference would be to remove
th
Here's a git branch with the backported changes in case anyone has time to
take a look this weekend:
https://github.com/toddlipcon/hadoop-common/tree/branch-2-QJM
There were a few conflicts due to patches committed in different orders,
and I had to pull in a couple other JIRAs along the way, but
+1 from me, too. I wanted to let it sit in trunk for a few weeks to see if
anyone found issues, but it's now been a bit over a month all the feedback
I've gotten so far has been good, tests have been stable, etc.
Unless anyone votes otherwise, I'll start backporting the patches into
branch-2.
Tod
+1 on having QJM in hadoop-2.0.3. Any rough estimate when this is targeted
for?
2012/11/15 Arun C Murthy
> On the heels of the planned 0.23.5 release (thanks Bobby & Thomas) I want
> to rollout a hadoop-2.0.3 release to reflect the growing stability of YARN.
>
> I'm hoping we can also release th
On the heels of the planned 0.23.5 release (thanks Bobby & Thomas) I want to
rollout a hadoop-2.0.3 release to reflect the growing stability of YARN.
I'm hoping we can also release the QJM along-with; hence I'd love to know an
ETA - Todd? Sanjay? Suresh?
One other thing which would be nice henc
43 matches
Mail list logo
