Jinjiang Ling created MAPREDUCE-7001:
Summary: Moving logging APIs over to slf4j in
hadoop-mapreduce-client-shuffle
Key: MAPREDUCE-7001
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7001
Pr
Jinjiang Ling created MAPREDUCE-7000:
Summary: Moving logging APIs over to slf4j in
hadoop-mapreduce-client-nativetask
Key: MAPREDUCE-7000
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7000
+1 (binding)
Tested the branch code and brought up services like sleep and httpd. Also
verified UI as well.
- Sunil
On Tue, Oct 31, 2017 at 1:36 AM Jian He wrote:
> Hi All,
>
> I would like to restart the vote for merging yarn-native-services to trunk.
> Since last vote, we have been working
Hi all,
With 3.0.0 GA around the corner (tx for the push, Andrew!), 2.9.0 RC out (tx
Arun / Subru!) and 2.8.2 (tx Junping!), I think it's high time we have a
discussion on how we manage our developmental bandwidth between 2.x line and
3.x lines.
Once 3.0 GA goes out, we will have two parallel
Hey Vinod,
I've cleaned up the RC directory as you requested.
Cheers
-Arun
On Fri, Nov 3, 2017 at 4:09 PM, Vinod Kumar Vavilapalli
wrote:
> Arun / Subru,
>
> Thanks for the great work!
>
> Few quick comments
> - Can you cleanup the RC folder to only have tar.gz and src.tar.gz and
> their sign
Hello Junping
Thanks for taking the time/effort to go through this. Including our reply
so that folks in the list have the full context.
> 1. It looks like we change from log4j to sel4j (HADOOP-12956) in 2.9
which is a huge incompatible change. Do we have consensus on this in
community (as I saw
Below is some findings from my recently run of JACC
(https://builds.apache.org/job/Hadoop-2.9-JACC/12/artifact/target/compat-check/report.html)
job against 2.9 and 2.8.2. I have discussed with Arun and Subru offline on
jdiff report who convinced me some of items are not a big concern. Just tried
Arun / Subru,
Thanks for the great work!
Few quick comments
- Can you cleanup the RC folder to only have tar.gz and src.tar.gz and their
signatures and delete everything else? So that it's easy to pick up the
important bits for the voters. For e.g, like this
http://people.apache.org/~vinodkv/
Hi folks,
Apache Hadoop 2.9.0 is the first stable release of Hadoop 2.9 line and
will be the latest stable/production release for Apache Hadoop - it
includes 30 New Features with 500+ subtasks, 407 Improvements, 787 Bug
fixes new fixed issues since 2.8.2 .
More information about the 2.
> At a minimum, it should at least be using it’s own maven module for a
> lot of the bits that generates it’s own maven jars so that we can split this
> functionality up at build/test time.
I expected this to be the case, but looks like it isn't.
There's lot of value in splitting the HDF
Thanks all for the great works!
+1 (Binding). Tried to use native services to build and run applications
successfully.
- Wangda
On Fri, Nov 3, 2017 at 11:50 AM, Arun Suresh wrote:
> +1 (binding)
>
> Cheers
> -Arun
>
> On Nov 3, 2017 11:44 AM, "Chandni Singh" wrote:
>
> > +1
> > Thanks,
> > Ch
Hi folks!
Thank you for sharing the design docs and the tremendous amount of work
that has gone into Ozone. I'm grateful that atleast someone is trying to
drastically improve HDFS.
*If* there is a meeting to discuss this merge, could I please also be
invited?
Have we ever thought about distribut
Konstantine,
Thanks for your comments, questions and feedback. I have attached a document
to the HDFS-7240 jira
that explains a design for scaling HDFS and how Ozone paves the way towards
the full solution.
https://issues.apache.org/jira/secure/attachment/12895963/HDFS%20Scalability%20and%2
> On Nov 3, 2017, at 12:08 PM, Stack wrote:
>
> On Sat, Oct 28, 2017 at 2:00 PM, Konstantin Shvachko
> wrote:
>
>> It is an interesting question whether Ozone should be a part of Hadoop.
>
> I don't see a direct answer to this question. Is there one? Pardon me if
> I've not seen it but I'm in
Hi Lei,
Thank you for your interest in Ozone. Let me answer each of the
specific questions.
> As the current state of Ozone implementation, what are the major
> benefits of using today’s Ozone over HDFS?
Scale - HDFS tops out at 500/700 million keys; Ozone primary
use case is to go beyond tha
On Sat, Oct 28, 2017 at 2:00 PM, Konstantin Shvachko
wrote:
> Hey guys,
>
> It is an interesting question whether Ozone should be a part of Hadoop.
>
I don't see a direct answer to this question. Is there one? Pardon me if
I've not seen it but I'm interested in the response.
I ask because IMO
+1 (binding)
Cheers
-Arun
On Nov 3, 2017 11:44 AM, "Chandni Singh" wrote:
> +1
> Thanks,
> Chandni
>
> From: Jian He
> Sent: Monday, October 30, 2017 1:49 PM
> To: yarn-...@hadoop.apache.org; Hdfs-dev; Hadoop Common;
> mapreduce-dev@hadoop.apache.org
>
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/579/
[Nov 3, 2017 12:15:33 AM] (Arun Suresh) HADOOP-15013. Fix ResourceEstimator
findbugs issues. (asuresh)
[Nov 3, 2017 12:39:23 AM] (subru) YARN-7432. Fix DominantResourceFairnessPolicy
serializable findbugs
18 matches
Mail list logo
