+1.
Thanks,
Subru
On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka wrote:
> +1
>
> -Akira
>
> On Wed, May 13, 2020 at 4:53 PM Elek, Marton wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Ha
+1
On Tue, Mar 3, 2020 at 11:43 AM Wangda Tan wrote:
> +1
>
> On Mon, Mar 2, 2020 at 8:50 PM Akira Ajisaka wrote:
>
> > +1
> >
> > -Akira
> >
> > On Tue, Mar 3, 2020 at 4:55 AM Ayush Saxena wrote:
> >
> > > +1 for marking 2.8 EOL
> > >
> > > -Ayush
> > >
> > > > On 03-Mar-2020, at 12:18 AM, We
+1.
Thanks,
Subru
On Thu, Oct 24, 2019 at 12:51 AM 张铎(Duo Zhang)
wrote:
> +1
>
> Akira Ajisaka 于2019年10月24日周四 下午3:21写道：
>
> > Hi folks,
> >
> > Both Ozone and Apache Submarine have separate repositories.
> > Can we remove these modules from hadoop-trunk?
> >
> > Regards,
> > Akira
> >
>
+1 (binding).
IIUC, there will not be an Ozone module in trunk anymore as that was my
only concern from the original discussion thread? IMHO, this should be the
default approach for new modules.
On Tue, Sep 17, 2019 at 9:58 AM Salvatore LaMendola (BLOOMBERG/ 731 LEX) <
slamendo...@bloomberg.net>
+1
On Wed, Aug 21, 2019 at 8:52 AM Kihwal Lee
wrote:
> +1
>
> Kihwal
>
> On Tue, Aug 20, 2019 at 10:03 PM Wangda Tan wrote:
>
> > Hi all,
> >
> > This is a vote thread to mark any versions smaller than 2.7 (inclusive),
> > and 3.0 EOL. This is based on discussions of [1]
> >
> > This discussion
Belated binding +1 from my side (on vacation).
Thanks Jonathan for initiating this.
-Subru
On Thu, Feb 7, 2019 at 6:13 PM Jonathan Hung wrote:
> My non-binding +1 to finish. This vote passes with 6 binding +1, 3
> non-binding +1, and no vetoes. We will make the changes as part
> of HADOOP-1571
+1.
On Tue, Dec 11, 2018 at 12:10 AM Mukul Kumar Singh
wrote:
> +1
> -Mukul
>
> On 12/11/18, 9:56 AM, "Weiwei Yang" wrote:
>
> +1
>
> On Tue, Dec 11, 2018 at 10:51 AM Anu Engineer <
> aengin...@hortonworks.com>
> wrote:
>
> > +1
> > --Anu
> >
> >
> > On 12/10/18,
The Project Management Committee (PMC) for Apache Hadoophas invited
Botong Huang to become a committer and we are pleased to announce that
he has accepted.
Being a committer enables easier contribution to theproject since
there is no need to go via the patchsubmission process. This should
enable be
Thanks Sunil for volunteering to lead the release effort. I am generally
supportive of a release but -1 on a 3.2 (prefer a 3.1.x) as feel we already
have too many branches to be maintained. I already see many commits are in
different branches with no apparent rationale, for e.g: 3.1 has commits
whi
ks
> >
> > ugly for two commits and we can live with it.
> >
> >
> > The revert restored the branch to Giovanni's intent. i.e. only
> >
> > YARN-8435 is applied. Verified there is no delta between hashes
> 0d9804d and
>
te:
>
>> +1
>>
>> On 5 July 2018 at 14:37, Subru Krishnan wrote:
>>
>> > Folks,
>> >
>> > There was a merge commit accidentally pushed to trunk, you can find the
>> > details in the mail thread [1].
>> >
>> > I have rai
Folks,
There was a merge commit accidentally pushed to trunk, you can find the
details in the mail thread [1].
I have raised an INFRA ticket [2] to reset/force push to clean up trunk.
Can we have a quick vote for INFRA sign-off to proceed as this is blocking
all commits?
Thanks,
Subru
[1]
http
Folks,
We (i.e. Microsoft) have started stabilization of 2.9 for our production
deployment. During planning, we realized that we need to backport 3.x
features to support GPUs (and more resource types like network IO) natively
as part of the upgrade. We'd like to share that work with the community.
Wrapping up the vote with my +1.
Deployed RC3 on a federated YARN cluster with 6 sub-clusters:
- ran multiple sample jobs
- enabled opportunistic containers and submitted more samples
- configured HDFS federation and reran jobs.
With 13 binding +1s and 7 non-binding +1s and no +/-1s, pleased to
Hi Folks,
Apache Hadoop 2.9.0 is the first release of Hadoop 2.9 line and will be the
starting release for Apache Hadoop 2.9.x line - it includes 30 New Features
with 500+ subtasks, 407 Improvements, 790 Bug fixes new fixed issues since
2.8.2.
More information about the 2.9.0 release plan can be
erations.
>
> Thanks,
> Mukul
>
>
>
>
>
>
> On 10/11/17, 7:09 AM, "Subru Krishnan" wrote:
>
> >Hi Folks,
> >
> >Apache Hadoop 2.9.0 is the first release of Hadoop 2.9 line and will be
> the
> >starting release for Apache Hadoop 2.9.x line - it
Hi Folks,
Apache Hadoop 2.9.0 is the first release of Hadoop 2.9 line and will be the
starting release for Apache Hadoop 2.9.x line - it includes 30 New Features
with 500+ subtasks, 407 Improvements, 790 Bug fixes new fixed issues since
2.8.2 .
More information about the 2.9.0 release plan can be
just add to your voting thread and release notes
> that 2.9.0 still needs to be tested downstream and so users may want to
> wait for subsequent point releases.
>
> Thanks
> +Vinod
>
> > On Nov 8, 2017, at 12:43 AM, Subru Krishnan wrote:
> >
> > We are canceling the RC
We are canceling the RC due to the issue that Rohith/Sunil identified. The
issue was difficult to track down as it only happens when you use IP for ZK
(works fine with host names) and moreover if ZK and RM are co-located on
same machine. We are hopeful to get the fix in tomorrow and roll out RC1.
>
> >> 2017-10-31 13:44 GMT-07:00 Arun Suresh :
> >>
> >>> Hello folks
> >>>
> >>> We just cut branch-2.9 since all the critical/blocker issues are now
> >>> resolved.
> >>> We plan to perform some sanity checks for the r
plan to perform some sanity checks for the rest of the week and cut
>> branch-2.9.0 and push out an RC0 by the end of the week.
>>
>> Kindly refrain from committing to branch-2.9 without giving us a heads up.
>>
>> @Junping, lets move the jdiff conversation to separate
We want to give heads up that we are going to cut branch-2.9 tomorrow
morning.
We are down to 3 blockers and they all are close to being committed (thanks
everyone):
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.9+Release
There are 4 other non-blocker JIRAs that are targeted for 2.9
Today was the feature freeze date and we are glad to inform that all the
major planned features are merged in branch-2:
https://cwiki.apache.org/confluence/display/HADOOP/Roadmap#Roadmap-Plannedfeatures
:
Kudos to everyone who pulled through multiple blockers and made this
happen. Special shoutout
Thanks Inigo for driving this.
+1 (binding).
I have been involved during the design and have reviewed a couple of
patches. I feel this is a good addition and is well aligned with YARN
Federation (YARN-2915).
We deployed the HDFS Router in our test cluster and mapped it against 2
clusters - one r
Folks,
Quick update on 2.9.0 release. Looks like we are looking at around a week
of delay in the feature freeze:
https://cwiki.apache.org/confluence/display/HADOOP/Roadmap
For feature owners, where the status is:
1. Green - no action required at this point.
2. Orange - revert with confirma
Folks,
With the release for 2.8, we would like to look ahead to 2.9 release as
there are many features/improvements in branch-2 (about 1062 commits), that
are in need of a release vechile.
Here's our first cut of the proposal from the YARN side:
1. Scheduler improvements (decoupling allocatio
26 matches
Mail list logo
