The Apache Chukwa team is proud to announce Apache Chukwa version 0.8.0.
Apache Chukwa is a tool for log collection and monitoring Apache Hadoop
clusters. Chukwa consists of a set of RESTful APIs and a browser-based
monitoring console UI.
The release bits are at: http://www.apache.org/dyn/closer.
The Apache Chukwa team is proud to announce Apache Chukwa version 0.7.0.
Apache Chukwa is a tool for log collection and monitoring Apache Hadoop
clusters. Chukwa consists of a set of RESTful APIs and a browser-based
monitoring console UI.
The release bits are at: http://www.apache.org/dyn/closer.
Chukwa team is happy to announce Chukwa 0.6.0 release.
Apache Chukwa provides a high level monitoring system for Hadoop. More
details about Chukwa can be found at http://chukwa.apache.org/
The highlight of this release includes Heatmap for visualizing system
activities, pipeline writer for impro
3, 4, 2 (binding)
regards,
Eric
On Fri, Mar 23, 2012 at 8:28 AM, Marcos Ortiz wrote:
> 1,2, 5
> Best wishes
>
>
> On 03/22/2012 03:56 AM, Konstantin Shvachko wrote:
>>
>>
>> On Mon, Mar 19, 2012 at 6:06 PM, Arun C Murthy
>> wrote:
>>>
>>> We've discussed several options:
>>>
>>> (1) Rename bran
Your Chukwa crew are pleased to announce the release of Chukwa 0.5.0.
Download it from your favorite Apache mirror [1].
Chukwa 0.5.0 is a major release with two years of accumulated features
and bugfixes. For a complete list of changes, see release notes [2].
-The Chukwa Team
P.S. Thanks goes o
+1
On Wed, Nov 16, 2011 at 4:49 PM, Owen O'Malley wrote:
> +1 for release future 2xx releases as 1.x.y.
>
> I believe the right mapping is:
> rename branch-0.20-security to branch-1
> copy branch-0.20-security-205 to branch-1.0
>
> Then the 1.0.x releases will come off of the branch-1.0 and branc
+1 on Matt's proposal.
On Wed, Nov 16, 2011 at 1:11 PM, Matt Foley wrote:
> I support giving all three active code branches a clean start, on an equal
> footing:
>
> - The next release of 0.20-security (formerly expected as "0.20.205.1") to
> be 1.0.0, establishing branch-1.0
> - The next release
Congratulation, Alejandro!
regards,
Eric Yang
On Sep 26, 2011, at 10:15 AM, Aaron T. Myers wrote:
> Congratulations, Alejandro! Very well-deserved. It's a pleasure working with
> you.
>
> --
> Aaron T. Myers
> Software Engineer, Cloudera
>
>
>
> On Mon,
sed by Hadoop server side only
> (JT/NN/TT/DN/SNN), but that is a different thing. Having a client side set
> of JARs would help handle this (MAPREDUCE-1638).
>
> Thoughts?
>
> Thanks.
>
> Alejandro
>
> On Thu, Aug 4, 2011 at 1:14 PM, Eric Yang wrote:
>
>&g
The jar files placement outside of lib directory is to ensure the project
generated jar files are not mixed with it's dependencies.
Hence, if another project tries to import current project's jar files without
dependencies, it is possible to do so.
regards,
Eric
On Aug 4, 2011, at 11:03 AM, Al
ommunity.
>
> On Wed, May 4, 2011 at 7:39 PM, Eric Yang wrote:
>> While the world demand agility, the "review then commit" process is
>> preventing progress
>> from happening. People end up having to generate multiple version of
>> patches to ensure
>&
will be much
easier for Hadoop to grow new developers.
Regards,
Eric
On 5/5/11 2:51 AM, "Tony Valderrama" wrote:
Hi, I just wanted to drop in a few thoughts from a new developer
working outside of the Hadoop developer community.
On Wed, May 4, 2011 at 7:39 PM, Eric Yang wrote:
&
PM, "Eli Collins" wrote:
On Wed, May 4, 2011 at 7:39 PM, Eric Yang wrote:
> If we reflect back and see how the development community end up in its
> current state for Hadoop. There are development rapidly happening and tested
> in all kind of organizations. However, Hadoop
If we reflect back and see how the development community end up in its current
state for Hadoop. There are development rapidly happening and tested in all
kind of organizations. However, Hadoop committers are only committing code
that are interested by the sponsored companies. People are codi
On 2/26/11 7:10 PM, "Konstantin Boudnik" wrote:
> On Sat, Feb 26, 2011 at 05:38PM, Eric Yang wrote:
>
> Furthermore, my Puppet knowledge is very limited and I am for sure no expert
> in maven. I have some concern however:
> - how to provide privileged access
> -
On 2/26/11 4:34 PM, "Konstantin Boudnik" wrote:
> Apparently you are talking about something else, but I will bite...
>
> On Sat, Feb 26, 2011 at 04:03PM, Eric Yang wrote:
>> The proposed test automation process hasn't been thought through. Apache
>> Hu
scussing patch validation and snapshot build
infrastructure.
On Sat, Feb 26, 2011 at 12:43, Eric Yang wrote:
> We should be very careful about the approach that we chosen for
> build/packaging. The current state of hadoop is coupled together due to lack
> of standardized RPC format
We should be very careful about the approach that we chosen for
build/packaging. The current state of hadoop is coupled together due to lack
of standardized RPC format. Once this issue is cleared, the community will
want to split hdfs and m/r into separated projects at some point. It may be
2/18/11 11:50 AM, "Doug Cutting" wrote:
> On 02/18/2011 11:09 AM, Eric Yang wrote:
>> FYI, Owen's design doc for HADOOP-6255 is also available in xml
>> format in the proposed patch. I think as long as there is a mean to
>> edit/revise the design doc, it should
FYI, Owen's design doc for HADOOP-6255 is also available in xml format in the
proposed patch. I think as long as there is a mean to edit/revise the design
doc, it should be fine right?
Regards,
Eric
On 2/18/11 10:39 AM, "Doug Cutting" wrote:
On 02/18/2011 09:48 AM, Mahadev Konar wrote:
> I a
On 2/18/11 8:24 AM, "Steve Loughran" wrote:
> On 17/02/2011 18:36, Eric Yang wrote:
>
>> I think the bigger concern is that Hadoop ecosystem does not have a standard
>> method in linking dependencies. Hbase depends on Zookeeper, and Pig depends
>> on Hado
The biggest hurtle in hadoop adoption is that there is no easy way to setup
a pseudo cluster on developer's machine. People are steering off course to
build additional simulation tools and validation tools. In practice, those
tools don't provide nearly enough insight in things that could go wrong
conventions, that might
help the incubator simplify this decision.
Result of the vote:
Option 1) Ant Elder, Eric Yang, William A. Rowe Jr.
Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin
Option 3) Bernd Fondermann
Owen O'Malley +1 on proposal
I am not sure about Chris Mattm
I have updated the proposal per Owen's request. I put Incubator in
Sponsoring Entity like other proposals.
Regards,
Eric
On 6/16/10 10:35 AM, "Owen O'Malley" wrote:
>
> On Jun 16, 2010, at 9:58 AM, Eric Yang wrote:
>
>> Please vote as to whether you
Please vote as to whether you think Chukwa should move to Apache incubator.
The proposal is posted at:
http://wiki.apache.org/incubator/ChukwaProposal
Thanks
Regards,
Eric
Please vote as to whether you think Chukwa should become a top-level
Apache project.
I've included below a draft board resolution. It lists all current
active Chukwa committers as initial members of the project management
committee (PMC) and myself, Eric Yang, as the initial chair.
Do the
Hi Kim,
Scribe works well for simple deployment. The complexity increases when
"central scribe server" is multi-machines deployment. Basically, it
requires a reverse proxy to load balance the data collection. (
http://www.cloudera.com/blog/2008/11/02/configuring-and-using-scribe-for-had
oop-log
+1
This is great for Chukwa to manage it's own release schedule and branches.
Regards,
Eric
On 2/24/09 1:28 PM, "Owen O'Malley" wrote:
> I'd like to propose Chukwa as a new Hadoop subproject. It is currently
> in Hadoop Core's contrib directory. The ini
28 matches
Mail list logo
