g<mailto:mapreduce-...@hadoop.apache.org>;
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
Cc: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>;
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>
Subject: Re: Planning Hadoop
>>
>>>>> I would like to nominate YARN-3832 as 2.6.1 candidate which is critical
>>>>> and I also saw it happened recently on a 2.6.0 cluster. Hope this is
>>> not
>>>>> too late.
>>>>>
>>>>> Thanks,
>>>&
cluster. Hope this is
>> not
>>>> too late.
>>>>
>>>> Thanks,
>>>>
>>>> Junping
>>>> ____________
>>>> From: Rich Haase
>>>> Sent: Thursday, August 06, 2015 1
ust 06, 2015 1:52 AM
> > > To: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> > > Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> > > Subject: Re: Planning Hadoop 2.6.1 release
> > >
> > > +1 to add those fixes.
> >
, 2015 1:52 AM
> > To: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> > Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> > Subject: Re: Planning Hadoop 2.6.1 release
> >
> > +1 to add those fixes.
> >
> >
> > Rich Haase | Sr. Software Engin
ailto:awils...@pandora.com]
>>> Sent: 05 August 2015 23:25
>>> To: common-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
>>> yarn-...@hadoop.apache.org
>>> Cc: hdfs-dev@hadoop.apache.org
>>> Subject: Re: Planning Hadoop 2.6.1 release
>>>
t;
>>
>> Thanks & Regards
>> Rohith Sharma K S
>>
>>
>> -Original Message-
>> From: Allan Wilson [mailto:awils...@pandora.com]
>> Sent: 05 August 2015 23:25
>> To: common-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
&
> -Original Message-
> From: Allan Wilson [mailto:awils...@pandora.com]
> Sent: 05 August 2015 23:25
> To: common-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
> yarn-...@hadoop.apache.org
> Cc: hdfs-dev@hadoop.apache.org
> Subject: Re: Planning Hadoop 2.6.1 release
&g
___
>> From: Rich Haase
>> Sent: Thursday, August 06, 2015 1:52 AM
>> To: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>> Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: Planning Hadoop
gt; Sent: Wednesday, August 05, 2015 10:42 AM
> To: yarn-...@hadoop.apache.org
> Cc: mapreduce-...@hadoop.apache.org; common-...@hadoop.apache.org;
> hdfs-dev@hadoop.apache.org
> Subject: Re: Planning Hadoop 2.6.1 release
>
> Can we add following two fixes to 2.6.1?
>
&g
anks,
>
> Junping
>
> From: Rich Haase
> Sent: Thursday, August 06, 2015 1:52 AM
> To: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> Subject: Re: Planning Hadoop 2.6.1 release
>
>
Added them both. Tx Wangda!
+Vinod
> On Aug 5, 2015, at 10:42 AM, Wangda Tan wrote:
>
> Can we add following two fixes to 2.6.1?
>
> https://issues.apache.org/jira/browse/YARN-2922 and
> https://issues.apache.org/jira/browse/YARN-3487.
>
> They're not fatal issue, but they can cause lots of i
yarn-...@hadoop.apache.org
Cc: hdfs-dev@hadoop.apache.org
Subject: Re: Planning Hadoop 2.6.1 release
Another +1 to add those fixes.
YARN-3487 bug can grind a large cluster to a halt repeatedly
-Allan
Allan Wilson | Sr. Software Engineer | Pandora m 919.841.2449 |
awils...@pandora.com
op.apache.org; hdfs-dev@hadoop.apache.org
> Subject: Re: Planning Hadoop 2.6.1 release
>
> +1 to add those fixes.
>
>
> Rich Haase | Sr. Software Engineer | Pandora
> m 303.887.1146 | rha...@pandora.com
>
>
>
>
> On 8/5/15, 11:42 AM, "Wangda Tan" wro
-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: Planning Hadoop 2.6.1 release
+1 to add those fixes.
Rich Haase | Sr. Software Engineer | Pandora
m 303.887.1146 | rha...@pandora.com
On 8/5/15, 11:42 AM, "Wangda Tan&qu
-...@hadoop.apache.org;
hdfs-dev@hadoop.apache.org
Subject: Re: Planning Hadoop 2.6.1 release
Can we add following two fixes to 2.6.1?
https://issues.apache.org/jira/browse/YARN-2922 and
https://issues.apache.org/jira/browse/YARN-3487.
They're not fatal issue, but they can cause lots of issue in a
+1 to add those fixes.
Rich Haase | Sr. Software Engineer | Pandora
m 303.887.1146 | rha...@pandora.com
On 8/5/15, 11:42 AM, "Wangda Tan" wrote:
>Can we add following two fixes to 2.6.1?
>
>https://issues.apache.org/jira/browse/YARN-2922 and
>https://issues.apache.org/jira/browse/YARN-3487.
Can we add following two fixes to 2.6.1?
https://issues.apache.org/jira/browse/YARN-2922 and
https://issues.apache.org/jira/browse/YARN-3487.
They're not fatal issue, but they can cause lots of issue in a large
cluster.
Thanks,
Wangda
On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee wrote:
> See
See my later update in the thread. HDFS-7704 is in the list.
Thanks,
Sangjin
On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote:
> Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and is
> not part of the candidate list. Removed HDFS-7916 fr
Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and is not
part of the candidate list. Removed HDFS-7916 from the list.
Thanks
+Vinod
> On Jul 24, 2015, at 6:32 PM, Sangjin Lee wrote:
>
> Out of the JIRAs we proposed, please remove HDFS-7916. I don't think it
> applies to 2.6
Tx for the list, Joep!
> Jiras not yet marked with 2.6.1-candidate that we'd like to see in 2.6.1:
A whole bunch of them already are marked so, presumably from my list. I’ve
added the remaining for discussion.
> HDFS-7281 (committed in 3.0)
This is an incompatible change, so not adding it.
>
Just for the completeness, the following JIRAs have already been committed
to branch-2.6 and thus will be part of 2.6.1:
HADOOP-11307
YARN-2375
HDFS-7425
HDFS-4882
HDFS-7489
HDFS-7503
HDFS-7443
HDFS-3443
HADOOP-11466
HDFS-7733
MAPREDUCE-6237
YARN-3251
HDFS-6153 reverted
On Fri, Jul 31, 2015 at 1
Thanks Akira.
I'd like to make one small correction. If we're getting HDFS-7704, then we
should also get HDFS-7916. My earlier comment was assuming HDFS-7704 was
not included in the list. But if is (and I think it should), then we should
also get HDFS-7916 as it addresses an important issue relate
Thanks Joep and your team members for creating the list. I really
appreciate your work. I looked your 'not yet marked with
2.6.1-candidate' list and categorized them.
1) Now marked as 2.6.1-candidate and I agree with you to keep it marked.
* HDFS-7213
* HDFS-7788
* HDFS-7884
* HDFS-7930
* YARN
Out of the JIRAs we proposed, please remove HDFS-7916. I don't think it
applies to 2.6.
Thanks,
Sangjin
On Wed, Jul 22, 2015 at 4:02 PM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote:
> I’ve added them all to the 2.6.1-candidate list. I included everything
> even though some of them a
I’ve added them all to the 2.6.1-candidate list. I included everything even
though some of them are major tickets. The list is getting large, we will have
to cut these down once we get down to the next phase of figuring out what to
include and what not to.
Thanks
+Vinod
> On Jul 21, 2015, at 2
Thanks Vinod for updating the candidate list.
I'd like to include the followings 12 JIRAs:
* YARN-3641
* YARN-3585
* YARN-2910
* HDFS-8431
* HDFS-7830
* HDFS-7763
* HDFS-7742
* HDFS-7235
* HDFS-7225
* MAPREDUCE-6324
* HADOOP-11934
* HADOOP-11491
Thanks,
Akira
On 7/18/15 11:13, Vinod Kumar Vavil
- I also have a bunch of patches that I’d like to include, will update them
right away.
I’ve just finished this. The latest 2.6.1-candidate list is up at 64 JIRAs.
Others, please look at the list and post anything else you’d like to get
included for 2.6.1.
Thanks
+Vinod
On Jul 15, 2015, at
apache.org>;
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>;
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>
Subject: Re: Planning Hadoop 2.6.1 release
Hi Akira,
Can we also include YARN-3242? YARN-3242 fixed a critical ZKRMStateStore
bug.
It will work bette
mapreduce-...@hadoop.apache.org>
Cc: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>;
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>;
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>
Subject: Re: Planning Hadoop 2.6.1 release
Hi Akira,
Can we a
y Battula
>>
>>
>> From: Zhihai Xu [z...@cloudera.com]
>> Sent: Wednesday, May 13, 2015 12:04 PM
>> To: mapreduce-...@hadoop.apache.org
>> Cc: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
>> hdfs-dev@hadoop.apache.o
Regards
> Brahma Reddy Battula
>
>
> From: Zhihai Xu [z...@cloudera.com]
> Sent: Wednesday, May 13, 2015 12:04 PM
> To: mapreduce-...@hadoop.apache.org
> Cc: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
> hdfs-dev@hadoop.apache.
h = fs.makeQualified(path);
>> FileContext fc = FileContext.getFileContext(path.toUri(),new
>> Configuration());
>>
>>
>>
>> Thanks & Regards
>> Brahma Reddy Battula
>>
>> From: Chris Nauroth [cnaur...
che.org
Subject: Re: Planning Hadoop 2.6.1 release
Thank you, Arpit. In addition, I suggest we include the following:
HADOOP-11333. Fix deadlock in DomainSocketWatcher when the notification
pipe is full
HADOOP-11604. Prevent ConcurrentModificationException while closing domain
sockets during shutdown
Thank you, Arpit. In addition, I suggest we include the following:
HADOOP-11333. Fix deadlock in DomainSocketWatcher when the notification
pipe is full
HADOOP-11604. Prevent ConcurrentModificationException while closing domain
sockets during shutdown of DomainSocketWatcher thread.
HADOOP-11648. S
HDFS candidates for back-porting to Hadoop 2.6.1. The first two were requested
in [1].
HADOOP-11674. oneByteBuf in CryptoInputStream and CryptoOutputStream should be
non static
HADOOP-11710. Make CryptoOutputStream behave like DFSOutputStream wrt
synchronization
HDFS-7009. Active NN and standb
There were several requests on the user lists [1] for a 2.6.1 release. I
got many offline comments too.
Planning to do a 2.6.1 release in a few weeks time. We already have a bunch
of tickets committed to 2.7.1. I created a filter [2] to tracking pending
tickets.
We need to collectively come up wi
37 matches
Mail list logo
