+1
On Wed, Dec 6, 2023 at 9:03 AM Chao Sun wrote:
> +1
>
> On Wed, Dec 6, 2023 at 8:39 AM Akira Ajisaka wrote:
> >
> > +1
> >
> >
> >
> > On Wed, Dec 6, 2023 at 1:10 PM Xiaoqiao He wrote:
> >
> > > Dear Hadoop devs,
> > >
> > > Given the feedback from the discussion thread [1], I'd like to
I am pleased to announce that Simbarashe Dzinamarira has been elected as a
committer on the Apache Hadoop project.
We appreciate all of Simbarashe's work, and look forward to his continued
contributions.
Congratulations and welcome !
Best Regards,
Inigo Goiri
(On behalf of the Apache Hadoop PMC)
I would also vote for targeting 3.4 and have a long term version of Java
there.
On Tue, Mar 28, 2023 at 11:52 AM Igor Dvorzhak
wrote:
> +1 to re-focusing on 3.4 branch and upgrading it to Java 11/17, instead of
> making potentially breaking changes to 3.3.
>
> On Tue, Mar 28, 2023 at 11:17 AM
+1 (Binding)
Deployed a cluster on Azure VMs with:
* 3 VMs with HDFS Namenodes and Routers
* 2 VMs with YARN Resource Managers
* 5 VMs with HDFS Datanodes and Node Managers
Tests:
* Executed Tergagen+Terasort+Teravalidate.
* Executed wordcount.
* Browsed through the Web UI.
On Fri, Jul 10,
I wouldn't go for #3 and always require a JIRA for a PR.
In general, I think we should state the best practices for using GitHub PRs.
There were some guidelines but they were kind of open
For example, adding always a link to the JIRA to the description.
I think PRs can have a template as a start.
+1
On Wed, Jul 17, 2019 at 4:17 AM Steve Loughran
wrote:
> +1 for squash and merge, with whoever does the merge adding the full commit
> message for the logs, with JIRA, contributor(s) etc
>
> One limit of the github process is that the author of the commit becomes
> whoever hit the squash
+1
On Tue, Feb 5, 2019 at 8:22 AM Masatake Iwasaki
wrote:
> +1
>
> Masatake Iwasaki
>
> On 2/4/19 18:13, Jonathan Hung wrote:
> > Hello,
> >
> > Starting a vote based on the discuss thread [1] for moving branch-2
> > precommit/nightly test builds to openjdk8. After this change, the test
> >
+1 (binding)
- Deployed a cluster with 3 NNs, 3 RMs and 1 DN/NM on Azure
- Tested the Active probe for the Load Balancer in front of the NNs and the
RMs
- Checked the NN, RBF, and RM Web UIs
- Executed a TeraGen, TeraSort and TeraValidate
- Executed a YARN service with a TensorFlow app on Docker
+1 (non-binding)
- Deployed a cluster with 3 NNs, 3 RMs and 1 DN/NM on Azure
- Tested the Active probe for the Load Balancer in front of the NNs and the
RMs
- Checked the NN, RBF, and RM Web UIs
- Executed a wordcount, TeraGen, TeraSort and TeraValidate
- Executed a YARN service with a
+1 (non-binding)
- Installed a full cluster from the tgz on Azure:
-- 2 NNs in HA.
-- 2 RMs in HA.
-- 2 Routers for RBF.
-- One worker with NM and DN.
- Verified Web UIs.
- Executed Teragen/Terasort/Teravalidate through RBF.
- Scaled up the cluster from 1 to 10 workers and executed the jobs again.
+1 (non binding)
* Deployed with 4 subclusters with HDFS Router-based federation.
* Executed DistCp across subclusters through the Router
* Checked documentation and tgz
On Tue, Apr 3, 2018 at 4:25 PM, Vinod Kumar Vavilapalli
wrote:
> We vote on the source code. The
Thank you very much Allen for making the Windows build work again.
We are going through the unit tests and fixing them for Windows (as you
said mostly paths).
We got a couple related patches in already; this will help us track
progress.
On Thu, Mar 15, 2018 at 10:15 AM, Allen Wittenauer
+1 (non-binding)
Deployed in a cluster with 48 nodes and 8 subclusters:
- YARN federation
- HDFS Router-based federation
- Yarn UI 2
Executed a few Pi job using both HDFS and YARN federation.
Everything worked correctly.
The YARN UI 2 showed the jobs, etc.
On Wed, Nov 15, 2017 at 2:05
Hi Subru,
We are also discussing the merge of HDFS-10467 (Router-based federation)
and we would like to target 2.9 to do a full release together with YARN
federation.
Chris Douglas already arranged the integration into trunk for 3.0.0 GA.
Regarding the points to cover:
1. API compatibility: we
14 matches
Mail list logo