Have anybody from the HDFS side of things had a chance to look at the OOM
that Roman was reporting?
Thanks.
On Wed, Jun 26, 2013 at 12:26 AM, Arun C Murthy wrote:
> Ok, the last of the blockers is done.
>
> I'll roll an RC tonight.
>
> thanks,
> Arun
>
> On Jun 20, 2013, at 2:40 PM, Arun C Mur
Ok, the last of the blockers is done.
I'll roll an RC tonight.
thanks,
Arun
On Jun 20, 2013, at 2:40 PM, Arun C Murthy wrote:
> I think I've shared this before, but here you go again…
>
> http://s.apache.org/hadoop-2.1.0-beta-blockers
>
> At this point, HADOOP-9421 seems like the most import
I think I've shared this before, but here you go again…
http://s.apache.org/hadoop-2.1.0-beta-blockers
At this point, HADOOP-9421 seems like the most important.
thanks,
Arun
On Jun 20, 2013, at 8:31 AM, Alejandro Abdelnur wrote:
> Arun,
>
> It seems there are still a few things to iron out b
Arun,
It seems there are still a few things to iron out before getting 2.1 out of
the door.
As RM for the release, would you mind sharing the current state of things
and your estimate on when it could happen?
Thanks.
On Wed, Jun 19, 2013 at 4:29 PM, Roman Shaposhnik wrote:
> On Tue, Jun 18,
On Tue, Jun 18, 2013 at 11:58 PM, Arun C Murthy wrote:
> Ping. Any luck?
Unfortunately I've ran into:
https://issues.apache.org/jira/browse/HADOOP-9654
which was caused by the unrelated memory pressure on the NN,
but it had an unfortunate side effect of making the rest of the
testing stuck.
; yarn-dev@hadoop.apache.org
Subject: Re: Heads up: branch-2.1-beta
Ping. Any luck?
On Jun 17, 2013, at 4:06 PM, Roman Shaposhnik wrote:
> On Sun, Jun 16, 2013 at 5:14 PM, Arun C Murthy wrote:
>> Roman,
>>
>> Is there a chance you can run the tests with the full stack bui
Ping. Any luck?
On Jun 17, 2013, at 4:06 PM, Roman Shaposhnik wrote:
> On Sun, Jun 16, 2013 at 5:14 PM, Arun C Murthy wrote:
>> Roman,
>>
>> Is there a chance you can run the tests with the full stack built against
>> branch-2.1-beta and help us know where we are?
>
> I will try to kick off
Roman,
Is there a chance you can run the tests with the full stack built against
branch-2.1-beta and help us know where we are?
thanks,
Arun
On Jun 16, 2013, at 4:50 PM, Arun C Murthy wrote:
> Responses inline:
>
> On Jun 16, 2013, at 1:04 PM, Roman Shaposhnik wrote:
>
>> But there's a bit
Responses inline:
On Jun 16, 2013, at 1:04 PM, Roman Shaposhnik wrote:
> But there's a bit of bad news too (or at least the news that need to
> be triaged). At
> this point I don't know whether the Hadoop code is to blame or the
> tests/components
> themselves -- all I know is that these tests pa
Arun, actually YARN-787 fixed the problem. Run those tests from trunk and
branch-2.1-beta HEADs without issues. Without YARN-787 they fail.
Thx
On Sun, Jun 16, 2013 at 12:03 PM, Arun C Murthy wrote:
> Alejandro,
>
> Can you please take a look at MAPREDUCE-5327? This is related to YARN-787.
>
Will do
FWIW: at least two people reported errors on that ticket once the patch had
been applied, so I'm not convinced it is correct.
On Jun 16, 2013, at 12:04 PM, Arun C Murthy wrote:
> HDFS-4866 was committed a couple of days ago - hence isn't showing up in my
> filters.
>
> Can you pleas
HDFS-4866 is marked as a blocker. A patch was submitted and applied, but it
only fixes compilation. As I marked on the ticket, the results remain unusable
due to linker issues.
On Jun 16, 2013, at 5:33 AM, Arun C Murthy wrote:
> Which one are you talking about Ralph? This doesn't show up on a
HDFS-4866 is marked as a blocker. A patch was submitted that lets it compile,
but it still results in an unusable state because you can't link to the
resulting code.
On Jun 16, 2013, at 5:33 AM, Arun C Murthy wrote:
> Which one are you talking about Ralph? This doesn't show up on any blocker
On Sat, Jun 15, 2013 at 8:19 AM, Alejandro Abdelnur wrote:
> If the intention is to get the release out in time for the Hadoop Summit we
> have a very tight schedule.
>
> Because the release vote runs for 7 days, we should have an RC latest
> Monday afternoon, and we should encourage folks to veri
HDFS-4866 was committed a couple of days ago - hence isn't showing up in my
filters.
Can you please file a new jira for the linker issues?
thanks,
Arun
On Jun 16, 2013, at 10:16 AM, Ralph Castain wrote:
> HDFS-4866 is marked as a blocker. A patch was submitted and applied, but it
> only fixes
Alejandro,
Can you please take a look at MAPREDUCE-5327? This is related to YARN-787.
thanks,
Arun
On Jun 16, 2013, at 8:56 AM, Alejandro Abdelnur wrote:
> Thanks Arun, I'll take care of committing YARN-752 and MAPREDUCE-5171
> around noon today (SUN noon PST).
>
> What is your take on YARN-7
Thanks Arun, I'll take care of committing YARN-752 and MAPREDUCE-5171
around noon today (SUN noon PST).
What is your take on YARN-791 & MAPREDUCE-5130?
On Sun, Jun 16, 2013 at 7:02 AM, Arun C Murthy wrote:
>
> On Jun 16, 2013, at 5:39 AM, Arun C Murthy wrote:
>
> >
> > On Jun 15, 2013, at 8:1
On Jun 16, 2013, at 5:39 AM, Arun C Murthy wrote:
>
> On Jun 15, 2013, at 8:19 AM, Alejandro Abdelnur wrote:
>>
>> Of the JIRAs in my laundry list for 2.1 the ones I would really want in are
>> YARN-752, MAPREDUCE-5171 & YARN-787.
>
> I agree YARN-787 needs to go in ASAP & is a blocker - I'm l
Karthik,
My apologies - I'll definitely spend time on this *today*.
Arun
On Jun 15, 2013, at 4:18 PM, Karthik Kambatla wrote:
> Re-posting here to the wider audience:
>
> HADOOP-9517 (Document Hadoop Compatibility): I believe I have incorporated
> all suggestions so far. It would be great if
On Jun 15, 2013, at 8:19 AM, Alejandro Abdelnur wrote:
>
> Of the JIRAs in my laundry list for 2.1 the ones I would really want in are
> YARN-752, MAPREDUCE-5171 & YARN-787.
I agree YARN-787 needs to go in ASAP & is a blocker - I'm looking at it right
now.
I'm ok with YARN-752 & MAPREDUCE-5171
Which one are you talking about Ralph? This doesn't show up on any blocker list.
http://s.apache.org/hadoop-blocker-bugs
Arun
On Jun 15, 2013, at 4:44 PM, Ralph Castain wrote:
> Not trying to be a pain, but I am trying to get clarification. The protocol
> buffer support is still broken. Do yo
Not trying to be a pain, but I am trying to get clarification. The protocol
buffer support is still broken. Do you intend to release 2.1 with that unfixed?
On Jun 15, 2013, at 4:18 PM, Karthik Kambatla wrote:
> Re-posting here to the wider audience:
>
> HADOOP-9517 (Document Hadoop Compatibil
Re-posting here to the wider audience:
HADOOP-9517 (Document Hadoop Compatibility): I believe I have incorporated
all suggestions so far. It would be great if people could take another look
at it. I ll iterate fast on any comments so we get this in by the time rest
of the code pieces are committed
If the intention is to get the release out in time for the Hadoop Summit we
have a very tight schedule.
Because the release vote runs for 7 days, we should have an RC latest
Monday afternoon, and we should encourage folks to verify & vote ASAP, so
if we need to cut a new RC we can do it on Tuesday
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 g
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 wrote:
> Arun,
>
> This sounds great. Following is the list of JIRAs I'd like to get in. Note
> th
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: beh
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 wor
We have started testing branch-2.1-beta and for most parts the code looks
very stable. We have deployed both secure and non-secure multinode clusters.
We had some minor hiccups with some of our e2e tests breaking due to
additional setsid info being logged by the bin scripts and errors while
buildi
On Thu, Jun 6, 2013 at 4:48 AM, Arun C Murthy 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 bran
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.
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 g
32 matches
Mail list logo
