Hi Bilwa,

I have commented on the jira's you mentioned. Based on the stability we can
plan this.But needs to be merged ASAP.



On Fri, Feb 19, 2021 at 5:20 PM bilwa st <stbi...@gmail.com> wrote:

> Hi Brahma,
>
> Can we have below features in 3.3.1 release? We have been using these
> features for a long time. They are stable and tested in bigger clusters.
>
> 1. Container reuse - https://issues.apache.org/jira/browse/MAPREDUCE-6749
> 2. Speculative attempts should not run on the same node -
> https://issues.apache.org/jira/browse/MAPREDUCE-7169
>
> Thanks,
> Bilwa
>
> On Thu, Feb 18, 2021, 1:49 PM Brahma Reddy Battula <bra...@apache.org>
> wrote:
>
>> Sorry for the late reply..
>>
>> I will come up with a plan.. Please let me know if anybody has some
>> features/improvements/bugs that need to be included.
>>
>> On Mon, Feb 15, 2021 at 9:39 PM Sunil Govindan <sun...@apache.org> wrote:
>>
>> > Hi Wei-Chiu,
>> >
>> > What will be the next steps here for 3.3.1 planning?
>> >
>> > Thanks
>> > Sunil
>> >
>> > On Mon, Feb 8, 2021 at 11:56 PM Stack <st...@duboce.net> wrote:
>> >
>> > > On Wed, Feb 3, 2021 at 6:41 AM Steve Loughran
>> > <ste...@cloudera.com.invalid
>> > > >
>> > > wrote:
>> > >
>> > > >
>> > > > Regarding blockers &c: how about we have a little hackathon where we
>> > try
>> > > > and get things in. This means a promise of review time from the
>> people
>> > > with
>> > > > commit rights and other people who understand the code (Stack?)
>> > > >
>> > > >
>> > >
>> > > I'm up for helping get 3.3.1 out (reviewing, hackathon, testing).
>> > > Thanks,
>> > > S
>> > >
>> > >
>> > >
>> > >
>> > > > -steve
>> > > >
>> > > > On Thu, 28 Jan 2021 at 06:48, Ayush Saxena <ayush...@gmail.com>
>> wrote:
>> > > >
>> > > > > +1
>> > > > > Just to mention we would need to release hadoop-thirdparty too
>> > before.
>> > > > > Presently we are using the snapshot version of it.
>> > > > >
>> > > > > -Ayush
>> > > > >
>> > > > > > On 28-Jan-2021, at 6:59 AM, Wei-Chiu Chuang <weic...@apache.org
>> >
>> > > > wrote:
>> > > > > >
>> > > > > > Hi all,
>> > > > > >
>> > > > > > Hadoop 3.3.0 was released half a year ago, and as of now we've
>> > > > > accumulated
>> > > > > > more than 400 changes in the branch-3.3. A number of
>> downstreamers
>> > > are
>> > > > > > eagerly waiting for 3.3.1 which addresses the guava version
>> > conflict
>> > > > > issue.
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%20in%20(HDFS%2C%20HADOOP%2C%20YARN%2C%20MAPREDUCE)%20and%20fixVersion%20in%20(3.3.1)%20and%20status%20%3D%20Resolved%20
>> > > > > >
>> > > > > > We should start the release work for 3.3.1 before the diff
>> becomes
>> > > even
>> > > > > > larger.
>> > > > > >
>> > > > > > I believe there are  currently only two real blockers for a
>> 3.3.1
>> > > > (using
>> > > > > > this filter
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%20in%20(HDFS%2C%20HADOOP%2C%20YARN%2C%20MAPREDUCE)%20AND%20cf%5B12310320%5D%20in%20(3.3.1)%20AND%20status%20not%20in%20(Resolved)%20ORDER%20BY%20priority%20DESC
>> > > > > > )
>> > > > > >
>> > > > > >
>> > > > > >   1. HDFS-15566 <
>> https://issues.apache.org/jira/browse/HDFS-15566>
>> > > > > >   2.
>> > > > > >      1. HADOOP-17112 <
>> > > > https://issues.apache.org/jira/browse/HADOOP-17112
>> > > > > >
>> > > > > >         2.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Is there anyone who would volunteer to be the 3.3.1 RM?
>> > > > > >
>> > > > > > Also, the HowToRelease wiki does not describe the ARM build
>> > process.
>> > > > > That's
>> > > > > > going to be important for future releases.
>> > > > >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
>> > > > > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>>
>> --
>>
>>
>>
>> --Brahma Reddy Battula
>>
>

-- 



--Brahma Reddy Battula

Reply via email to