Re: metrics consumer logging stormUI data

[Raphael Hsieh]

Thanks Harsha and Otis for your prompt responses.
I'm looking to somehow log these metrics to use for an in-house monitoring
system. I don't want to get user provided metrics just yet.

>From what I've gathered from the big data cookbook is that I just want to
create a metrics consumer to read these metrics and print it out to a log
file. In order to do this I have added to my config:

config.registerMetricsConsumer(LoggingMetricsConsumer.class, 2);

which should create a loggingMetricsConsumer with a parallelism of 2 (I
believe). I was lead to believe that these logs would be put in a file
called "metrics.log". However after adding this to my topology I have been
unable to find such a log.
If someone could explain to me what I might be missing that would be great.

Thanks!

On Fri, Sep 19, 2014 at 4:27 PM, Gezim Musliaj  wrote:

> Hey Otis, I was just registered at sematext and I can say that this is
> what I have been looking for.I have just one question, what about the
> delays between the SPM and the Storm Cluster (if they do exist), whats the
> worst case? I mean because these metrics are not calculated locally, but
> using an internet connection.
> Thanks !
>
> On Sat, Sep 20, 2014 at 1:15 AM, Otis Gospodnetic <
> otis.gospodne...@gmail.com> wrote:
>
>> Raphael,
>>
>> Not sure if this is what you are after, but SPM
>>  will collect and graph all Storm metrics, let
>> you do alerting and anomaly detection on them, etc.  If you want to graph
>> custom metrics (e.g. something from your bolts), you can send them in as 
>> custom
>> metrics
>>  and
>> again graph them, alert on them, do anomaly detection on them, stick them
>> on dashboards, etc.  If you want to emit events from your bolts, you can send
>> events to SPM
>> ,
>> too, or you can send them to Logsene ...
>> can be handy for correlation with alerts and performance graphs when
>> troubleshooting.  Here are some Storm metrics graph:
>> http://blog.sematext.com/2014/01/30/announcement-apache-storm-monitoring-in-spm/
>>
>>
>> I hope this helps.
>>
>> Otis
>> --
>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>> Solr & Elasticsearch Support * http://sematext.com/
>>
>>
>> On Fri, Sep 19, 2014 at 6:12 PM, Raphael Hsieh 
>> wrote:
>>
>>> Hi,
>>> Using Storm/Trident, how do I register a metrics consumer to log the
>>> data I get in the StormUI ?
>>> I want to look at historical data of my topology, for example the
>>> execute latency of the topology over time, as this would give me good
>>> insight as to where things might be going wrong when the system breaks.
>>>
>>> I have been following the steps outlined in the BigData CookBook here:
>>> http://www.bigdata-cookbook.com/post/72320512609/storm-metrics-how-to
>>>
>>> However I am not wanting to create my own metrics, instead I just want
>>> to log the metrics that already exist built in to Storm. It is unclear to
>>> me how I am supposed to go about doing that.
>>>
>>> Thanks
>>>
>>> --
>>> Raphael Hsieh
>>>
>>>
>>>
>>>
>>
>>
>


-- 
Raphael Hsieh

Re: metrics consumer logging stormUI data

[Harsha]

Hi Raphael,

I tested it with wordcounttopology under examples.

conf.registerMetricsConsumer(LoggingMetricsConsumer.class,
2);

I do see the metrics added to the logs/metrics.log. metrics.log
should be present by default under storm/logs dir.

-Harsha









On Mon, Sep 22, 2014, at 09:24 AM, Raphael Hsieh wrote:

Thanks Harsha and Otis for your prompt responses.
I'm looking to somehow log these metrics to use for an in-house
monitoring system. I don't want to get user provided metrics
just yet.

>From what I've gathered from the big data cookbook is that I
just want to create a metrics consumer to read these metrics
and print it out to a log file. In order to do this I have
added to my config:

config.registerMetricsConsumer(LoggingMetricsConsumer.class,
2);

which should create a loggingMetricsConsumer with a parallelism
of 2 (I believe). I was lead to believe that these logs would
be put in a file called "metrics.log". However after adding
this to my topology I have been unable to find such a log.
If someone could explain to me what I might be missing that
would be great.

Thanks!

On Fri, Sep 19, 2014 at 4:27 PM, Gezim Musliaj
<[1]gmusl...@gmail.com> wrote:

Hey Otis, I was just registered at sematext and I can say that
this is what I have been looking for.I have just one question,
what about the delays between the SPM and the Storm Cluster (if
they do exist), whats the worst case? I mean because these
metrics are not calculated locally, but using an internet
connection.

Thanks !


On Sat, Sep 20, 2014 at 1:15 AM, Otis Gospodnetic
<[2]otis.gospodne...@gmail.com> wrote:

Raphael,

Not sure if this is what you are after, but [3]SPM will collect
and graph all Storm metrics, let you do alerting and anomaly
detection on them, etc.  If you want to graph custom metrics
(e.g. something from your bolts), you can send them in as
[4]custom metrics and again graph them, alert on them, do
anomaly detection on them, stick them on dashboards, etc.  If
you want to emit events from your bolts, you can [5]send events
to SPM, too, or you can send them to [6]Logsene... can be handy
for correlation with alerts and performance graphs when
troubleshooting.  Here are some Storm metrics graph:
[7]http://blog.sematext.com/2014/01/30/announcement-apache-stor
m-monitoring-in-spm/

I hope this helps.

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log
Management
Solr & Elasticsearch Support * [8]http://sematext.com/


On Fri, Sep 19, 2014 at 6:12 PM, Raphael Hsieh
<[9]raffihs...@gmail.com> wrote:

Hi,
Using Storm/Trident, how do I register a metrics consumer to
log the data I get in the StormUI ?
I want to look at historical data of my topology, for example
the execute latency of the topology over time, as this would
give me good insight as to where things might be going wrong
when the system breaks.

I have been following the steps outlined in the BigData
CookBook
here: [10]http://www.bigdata-cookbook.com/post/72320512609/stor
m-metrics-how-to

However I am not wanting to create my own metrics, instead I
just want to log the metrics that already exist built in to
Storm. It is unclear to me how I am supposed to go about doing
that.

Thanks

--
Raphael Hsieh








--
Raphael Hsieh

References

1. mailto:gmusl...@gmail.com
2. mailto:otis.gospodne...@gmail.com
3. http://sematext.com/spm/
4. https://sematext.atlassian.net/wiki/display/PUBSPM/Custom+Metrics
5. https://sematext.atlassian.net/wiki/display/PUBSPM/Events+Integration
6. http://www.sematext.com/logsene/
7. 
http://blog.sematext.com/2014/01/30/announcement-apache-storm-monitoring-in-spm/
8. http://sematext.com/
9. mailto:raffihs...@gmail.com
  10. http://www.bigdata-cookbook.com/post/72320512609/storm-metrics-how-to

Re: metrics consumer logging stormUI data

[Otis Gospodnetic]

Hi Gezim,

On Fri, Sep 19, 2014 at 7:27 PM, Gezim Musliaj  wrote:

> Hey Otis, I was just registered at sematext and I can say that this is
> what I have been looking for.I have just one question, what about the
> delays between the SPM and the Storm Cluster (if they do exist), whats the
> worst case? I mean because these metrics are not calculated locally, but
> using an internet connection.
>

The worst case is that somebody unplugs your servers from the network, but
if that happens you have bigger problems to deal with.  In all seriousness,
Storm (local) => SPM (remote/cloud/saas) is not really a problem -- lots of
people successfully use SPM for monitoring Storm, Hadoop, Kafka, and other
types of systems.

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/




> Thanks !
>
> On Sat, Sep 20, 2014 at 1:15 AM, Otis Gospodnetic <
> otis.gospodne...@gmail.com> wrote:
>
>> Raphael,
>>
>> Not sure if this is what you are after, but SPM
>>  will collect and graph all Storm metrics, let
>> you do alerting and anomaly detection on them, etc.  If you want to graph
>> custom metrics (e.g. something from your bolts), you can send them in as 
>> custom
>> metrics
>>  and
>> again graph them, alert on them, do anomaly detection on them, stick them
>> on dashboards, etc.  If you want to emit events from your bolts, you can send
>> events to SPM
>> ,
>> too, or you can send them to Logsene ...
>> can be handy for correlation with alerts and performance graphs when
>> troubleshooting.  Here are some Storm metrics graph:
>> http://blog.sematext.com/2014/01/30/announcement-apache-storm-monitoring-in-spm/
>>
>>
>> I hope this helps.
>>
>> Otis
>> --
>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>> Solr & Elasticsearch Support * http://sematext.com/
>>
>>
>> On Fri, Sep 19, 2014 at 6:12 PM, Raphael Hsieh 
>> wrote:
>>
>>> Hi,
>>> Using Storm/Trident, how do I register a metrics consumer to log the
>>> data I get in the StormUI ?
>>> I want to look at historical data of my topology, for example the
>>> execute latency of the topology over time, as this would give me good
>>> insight as to where things might be going wrong when the system breaks.
>>>
>>> I have been following the steps outlined in the BigData CookBook here:
>>> http://www.bigdata-cookbook.com/post/72320512609/storm-metrics-how-to
>>>
>>> However I am not wanting to create my own metrics, instead I just want
>>> to log the metrics that already exist built in to Storm. It is unclear to
>>> me how I am supposed to go about doing that.
>>>
>>> Thanks
>>>
>>> --
>>> Raphael Hsieh
>>>
>>>
>>>
>>>
>>
>>
>

Re: metrics consumer logging stormUI data

[Raphael Hsieh]

Hi Harsha,
Did you have to bind the metrics consumer to the default StormUI metrics at
all? Or do those automagically get included ?

Thanks!

On Mon, Sep 22, 2014 at 10:33 AM, Otis Gospodnetic <
otis.gospodne...@gmail.com> wrote:

> Hi Gezim,
>
> On Fri, Sep 19, 2014 at 7:27 PM, Gezim Musliaj  wrote:
>
>> Hey Otis, I was just registered at sematext and I can say that this is
>> what I have been looking for.I have just one question, what about the
>> delays between the SPM and the Storm Cluster (if they do exist), whats the
>> worst case? I mean because these metrics are not calculated locally, but
>> using an internet connection.
>>
>
> The worst case is that somebody unplugs your servers from the network, but
> if that happens you have bigger problems to deal with.  In all seriousness,
> Storm (local) => SPM (remote/cloud/saas) is not really a problem -- lots of
> people successfully use SPM for monitoring Storm, Hadoop, Kafka, and other
> types of systems.
>
> Otis
> --
> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
> Solr & Elasticsearch Support * http://sematext.com/
>
>
>
>
>> Thanks !
>>
>> On Sat, Sep 20, 2014 at 1:15 AM, Otis Gospodnetic <
>> otis.gospodne...@gmail.com> wrote:
>>
>>> Raphael,
>>>
>>> Not sure if this is what you are after, but SPM
>>>  will collect and graph all Storm metrics,
>>> let you do alerting and anomaly detection on them, etc.  If you want to
>>> graph custom metrics (e.g. something from your bolts), you can send them in
>>> as custom metrics
>>>  and
>>> again graph them, alert on them, do anomaly detection on them, stick them
>>> on dashboards, etc.  If you want to emit events from your bolts, you can 
>>> send
>>> events to SPM
>>> ,
>>> too, or you can send them to Logsene ...
>>> can be handy for correlation with alerts and performance graphs when
>>> troubleshooting.  Here are some Storm metrics graph:
>>> http://blog.sematext.com/2014/01/30/announcement-apache-storm-monitoring-in-spm/
>>>
>>>
>>> I hope this helps.
>>>
>>> Otis
>>> --
>>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>>> Solr & Elasticsearch Support * http://sematext.com/
>>>
>>>
>>> On Fri, Sep 19, 2014 at 6:12 PM, Raphael Hsieh 
>>> wrote:
>>>
 Hi,
 Using Storm/Trident, how do I register a metrics consumer to log the
 data I get in the StormUI ?
 I want to look at historical data of my topology, for example the
 execute latency of the topology over time, as this would give me good
 insight as to where things might be going wrong when the system breaks.

 I have been following the steps outlined in the BigData CookBook here:
 http://www.bigdata-cookbook.com/post/72320512609/storm-metrics-how-to

 However I am not wanting to create my own metrics, instead I just want
 to log the metrics that already exist built in to Storm. It is unclear to
 me how I am supposed to go about doing that.

 Thanks

 --
 Raphael Hsieh




>>>
>>>
>>
>


-- 
Raphael Hsieh

Re: metrics consumer logging stormUI data

[Harsha]

Here is what I see in the metrics.log

2014-09-22 09:44:31,321 731751411404271
localhost:6703 19:split   __transfer-count
{default=2680}

2014-09-22 09:44:31,321 731751411404271
localhost:6703 19:split   __execute-latency
{spout:default=0.0}

2014-09-22 09:44:31,321 731751411404271
localhost:6703 19:split   __fail-count{}

2014-09-22 09:44:31,321 731751411404271
localhost:6703 19:split   __emit-count
{default=2680}

2014-09-22 09:44:31,321 731751411404271
localhost:6703 19:split   __execute-count
{spout:default=420}

2014-09-22 09:44:31,352 731791411404271
localhost:6703 22:split   __ack-count
{spout:default=420}

2014-09-22 09:44:31,352 731791411404271
localhost:6703 22:split   __sendqueue
{write_pos=2679, capacity=1024, read_pos=2679, population=0}

I do see all the UI related counts coming in the metrics.log.



-Harsha





On Mon, Sep 22, 2014, at 10:41 AM, Raphael Hsieh wrote:

Hi Harsha,
Did you have to bind the metrics consumer to the default
StormUI metrics at all? Or do those automagically get included
?

Thanks!

On Mon, Sep 22, 2014 at 10:33 AM, Otis Gospodnetic
<[1]otis.gospodne...@gmail.com> wrote:

Hi Gezim,

On Fri, Sep 19, 2014 at 7:27 PM, Gezim Musliaj
<[2]gmusl...@gmail.com> wrote:

Hey Otis, I was just registered at sematext and I can say that
this is what I have been looking for.I have just one question,
what about the delays between the SPM and the Storm Cluster (if
they do exist), whats the worst case? I mean because these
metrics are not calculated locally, but using an internet
connection.


The worst case is that somebody unplugs your servers from the
network, but if that happens you have bigger problems to deal
with.  In all seriousness, Storm (local) => SPM
(remote/cloud/saas) is not really a problem -- lots of people
successfully use SPM for monitoring Storm, Hadoop, Kafka, and
other types of systems.

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log
Management
Solr & Elasticsearch Support * [3]http://sematext.com/



Thanks !


On Sat, Sep 20, 2014 at 1:15 AM, Otis Gospodnetic
<[4]otis.gospodne...@gmail.com> wrote:

Raphael,

Not sure if this is what you are after, but [5]SPM will collect
and graph all Storm metrics, let you do alerting and anomaly
detection on them, etc.  If you want to graph custom metrics
(e.g. something from your bolts), you can send them in as
[6]custom metrics and again graph them, alert on them, do
anomaly detection on them, stick them on dashboards, etc.  If
you want to emit events from your bolts, you can [7]send events
to SPM, too, or you can send them to [8]Logsene... can be handy
for correlation with alerts and performance graphs when
troubleshooting.  Here are some Storm metrics graph:
[9]http://blog.sematext.com/2014/01/30/announcement-apache-stor
m-monitoring-in-spm/

I hope this helps.

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log
Management
Solr & Elasticsearch Support * [10]http://sematext.com/


On Fri, Sep 19, 2014 at 6:12 PM, Raphael Hsieh
<[11]raffihs...@gmail.com> wrote:

Hi,
Using Storm/Trident, how do I register a metrics consumer to
log the data I get in the StormUI ?
I want to look at historical data of my topology, for example
the execute latency of the topology over time, as this would
give me good insight as to where things might be going wrong
when the system breaks.

I have been following the steps outlined in the BigData
CookBook
here: [12]http://www.bigdata-cookbook.com/post/72320512609/stor
m-metrics-how-to

However I am not wanting to create my own metrics, instead I
just want to log the metrics that already exist built in to
Storm. It is unclear to me how I am supposed to go about doing
that.

Thanks

--
Raphael Hsieh











--
Raphael Hsieh

References

1. mailto:otis.gospodne...@gmail.com
2. mailto:gmusl...@gmail.com
3. http://sematext.com/
4. mailto:otis.gospodne...@gmail.com
5. http://sematext.com/spm/
6. https://sematext.atlassian.net/wiki/display/PUBSPM/Custom+Metrics
7. https://sematext.atlassian.net/wiki/display/PUBSPM/Events+Integration
8. http://www.sematext.com/logsene/
9. 
http://blog.sematext.com/2014/01/30/announcement-apache-storm-monitoring-in-spm/
  10. http://sematext.com/
  11. mailto:raffihs...@gmail.com
  12. http://www.bigdata-cookbook.com/post/72320512609/storm-metrics-how-to

Apache Storm Graduation to a TLP

[P. Taylor Goetz]

I’m pleased to announce that Apache Storm has graduated to a Top-Level Project 
(TLP), and I’d like to thank everyone in the Storm community for your 
contributions and help in achieving this important milestone.

As part of the graduation process, a number of infrastructure changes have 
taken place:

New website url: http://storm.apache.org

New git repo urls:

https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)

g...@github.com:apache/storm.git
-or-
https://github.com/apache/storm.git (for github pull requests)

Mailing Lists:
If you are already subscribed, you’re subscription has been migrated. New 
messages should be sent to the new address:

[list]@storm.apache.org

This includes any subscribe/unsubscribe requests.

Note: The mail-archives.apache.org site will not reflect these changes until 
October 1.


Most of these changes have already occurred and are seamless. Please update 
your git remotes and address books accordingly.

- Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Apache Storm Graduation to a TLP

[Corey Nolet]

Congrats!

On Mon, Sep 22, 2014 at 5:16 PM, P. Taylor Goetz  wrote:

> I’m pleased to announce that Apache Storm has graduated to a Top-Level
> Project (TLP), and I’d like to thank everyone in the Storm community for
> your contributions and help in achieving this important milestone.
>
> As part of the graduation process, a number of infrastructure changes have
> taken place:
>
> *New website url:* http://storm.apache.org
>
> *New git repo urls:*
>
> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>
> g...@github.com:apache/storm.git
> -or-
> https://github.com/apache/storm.git (for github pull requests)
>
> *Mailing Lists:*
> If you are already subscribed, you’re subscription has been migrated. New
> messages should be sent to the new address:
>
> [list]@storm.apache.org
>
> This includes any subscribe/unsubscribe requests.
>
> Note: The mail-archives.apache.org site will not reflect these changes
> until October 1.
>
>
> Most of these changes have already occurred and are seamless. Please
> update your git remotes and address books accordingly.
>
> - Taylor
>

Re: Apache Storm Graduation to a TLP

[Guillaume Conte]

+1 Congrats!

From: Corey Nolet mailto:cjno...@gmail.com>>
Reply-To: 
"user@storm.incubator.apache.org" 
mailto:user@storm.incubator.apache.org>>
Date: Monday, September 22, 2014 at 11:33 PM
To: "user@storm.incubator.apache.org" 
mailto:user@storm.incubator.apache.org>>
Cc: "d...@storm.incubator.apache.org" 
mailto:d...@storm.incubator.apache.org>>
Subject: Re: Apache Storm Graduation to a TLP

Congrats!

On Mon, Sep 22, 2014 at 5:16 PM, P. Taylor Goetz 
mailto:ptgo...@gmail.com>> wrote:
I’m pleased to announce that Apache Storm has graduated to a Top-Level Project 
(TLP), and I’d like to thank everyone in the Storm community for your 
contributions and help in achieving this important milestone.

As part of the graduation process, a number of infrastructure changes have 
taken place:

New website url: http://storm.apache.org

New git repo urls:

https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)

g...@github.com:apache/storm.git
-or-
https://github.com/apache/storm.git (for github pull requests)

Mailing Lists:
If you are already subscribed, you’re subscription has been migrated. New 
messages should be sent to the new address:

[list]@storm.apache.org

This includes any subscribe/unsubscribe requests.

Note: The mail-archives.apache.org site will 
not reflect these changes until October 1.


Most of these changes have already occurred and are seamless. Please update 
your git remotes and address books accordingly.

- Taylor

Re: Apache Storm Graduation to a TLP

[Gezim Musliaj]

Congrats!

On Mon, Sep 22, 2014 at 11:41 PM, Guillaume Conte 
wrote:

>  +1 Congrats!
>
>   From: Corey Nolet 
> Reply-To: "user@storm.incubator.apache.org" <
> user@storm.incubator.apache.org>
> Date: Monday, September 22, 2014 at 11:33 PM
> To: "user@storm.incubator.apache.org" 
> Cc: "d...@storm.incubator.apache.org" 
> Subject: Re: Apache Storm Graduation to a TLP
>
>   Congrats!
>
> On Mon, Sep 22, 2014 at 5:16 PM, P. Taylor Goetz 
> wrote:
>
>> I’m pleased to announce that Apache Storm has graduated to a Top-Level
>> Project (TLP), and I’d like to thank everyone in the Storm community for
>> your contributions and help in achieving this important milestone.
>>
>>  As part of the graduation process, a number of infrastructure changes
>> have taken place:
>>
>>  *New website url:* http://storm.apache.org
>>
>>  *New git repo urls:*
>>
>>  https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>>
>>  g...@github.com:apache/storm.git
>> -or-
>> https://github.com/apache/storm.git (for github pull requests)
>>
>>  *Mailing Lists:*
>> If you are already subscribed, you’re subscription has been migrated. New
>> messages should be sent to the new address:
>>
>>  [list]@storm.apache.org
>>
>>  This includes any subscribe/unsubscribe requests.
>>
>>  Note: The mail-archives.apache.org site will not reflect these changes
>> until October 1.
>>
>>
>>  Most of these changes have already occurred and are seamless. Please
>> update your git remotes and address books accordingly.
>>
>>  - Taylor
>>
>
>

Re: Apache Storm Graduation to a TLP

[Shaikh Riyaz]

Congrats!

Regards,
RIyaz

On Tue, Sep 23, 2014 at 12:16 AM, P. Taylor Goetz  wrote:

> I’m pleased to announce that Apache Storm has graduated to a Top-Level
> Project (TLP), and I’d like to thank everyone in the Storm community for
> your contributions and help in achieving this important milestone.
>
> As part of the graduation process, a number of infrastructure changes have
> taken place:
>
> *New website url:* http://storm.apache.org
>
> *New git repo urls:*
>
> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>
> g...@github.com:apache/storm.git
> -or-
> https://github.com/apache/storm.git (for github pull requests)
>
> *Mailing Lists:*
> If you are already subscribed, you’re subscription has been migrated. New
> messages should be sent to the new address:
>
> [list]@storm.apache.org
>
> This includes any subscribe/unsubscribe requests.
>
> Note: The mail-archives.apache.org site will not reflect these changes
> until October 1.
>
>
> Most of these changes have already occurred and are seamless. Please
> update your git remotes and address books accordingly.
>
> - Taylor
>



-- 
Regards,

Riyaz

Re: Apache Storm Graduation to a TLP

[임정택]

Congrats!

2014년 9월 23일 화요일, P. Taylor Goetz님이 작성한 메시지:

> I’m pleased to announce that Apache Storm has graduated to a Top-Level
> Project (TLP), and I’d like to thank everyone in the Storm community for
> your contributions and help in achieving this important milestone.
>
> As part of the graduation process, a number of infrastructure changes have
> taken place:
>
> *New website url:* http://storm.apache.org
>
> *New git repo urls:*
>
> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>
> g...@github.com:apache/storm.git
> -or-
> https://github.com/apache/storm.git (for github pull requests)
>
> *Mailing Lists:*
> If you are already subscribed, you’re subscription has been migrated. New
> messages should be sent to the new address:
>
> [list]@storm.apache.org
>
> This includes any subscribe/unsubscribe requests.
>
> Note: The mail-archives.apache.org site will not reflect these changes
> until October 1.
>
>
> Most of these changes have already occurred and are seamless. Please
> update your git remotes and address books accordingly.
>
> - Taylor
>


-- 
Name : 임 정택
Blog : http://www.heartsavior.net / http://dev.heartsavior.net
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior

Local cluster zookeeper exception

[Jiang Jacky]

Hi, Guys
I am trying to run the test from my local cluster, but I get the exception
java.lang.ClassNotFoundException:
org.apache.zookeeper.server.NIOServerCnxnFactory

I have read some articles, it seems the version of zookeeper and storm, but
I am using the latest version of zookeeper(3.4.5) and latest version of
storm (0.9.2) it still doesn't work.

Can someone share some experience?
Thanks

Re: Local cluster zookeeper exception

[Vikas Agarwal]

I faced same exception and it turned out that it was version issue of
zookeeper. We are using maven and one of child dependency reference another
version of zookeeper which caused the issue. You can check dependency
hierarchy in eclipse to be sure that this is not the issue.

On Tue, Sep 23, 2014 at 4:32 AM, Jiang Jacky  wrote:

> Hi, Guys
> I am trying to run the test from my local cluster, but I get the exception
> java.lang.ClassNotFoundException:
> org.apache.zookeeper.server.NIOServerCnxnFactory
>
> I have read some articles, it seems the version of zookeeper and storm,
> but I am using the latest version of zookeeper(3.4.5) and latest version of
> storm (0.9.2) it still doesn't work.
>
> Can someone share some experience?
> Thanks
>



-- 
Regards,
Vikas Agarwal
91 – 9928301411

InfoObjects, Inc.
Execution Matters
http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
+1 (408) 988-2000 Work
+1 (408) 716-2726 Fax

Storm performing very slow

[Kushan Maskey]

I am trying to load 20 M records into Cassandra database through
Kafka-Storm. I am able to post all the data in 5 mins into Kafka. But
reading it from storm and inserting into Cassandra, Couch and Solr is kind
of very slow. It has been running for past 5 hours and so far only 2
Million records.

How do I make the storm perform faster? Coz in this pace it will take
couple of days to load all the data.

--
Kushan Maskey

Re: Local cluster zookeeper exception

[Jiang Jacky]

you are right, I delete the zookeeper dependency in the storm-core, the
everything works!

2014-09-22 21:38 GMT-04:00 Vikas Agarwal :

> I faced same exception and it turned out that it was version issue of
> zookeeper. We are using maven and one of child dependency reference another
> version of zookeeper which caused the issue. You can check dependency
> hierarchy in eclipse to be sure that this is not the issue.
>
> On Tue, Sep 23, 2014 at 4:32 AM, Jiang Jacky  wrote:
>
>> Hi, Guys
>> I am trying to run the test from my local cluster, but I get the exception
>> java.lang.ClassNotFoundException:
>> org.apache.zookeeper.server.NIOServerCnxnFactory
>>
>> I have read some articles, it seems the version of zookeeper and storm,
>> but I am using the latest version of zookeeper(3.4.5) and latest version of
>> storm (0.9.2) it still doesn't work.
>>
>> Can someone share some experience?
>> Thanks
>>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>

Re: Storm performing very slow

[Michael Rose]

Storm is not your bottleneck. Check your Storm code to 1) ensure you're
parallelizing your writes and 2) you're batching writes to your external
resources if possible. Some quick napkin math shows you only doing 110
writes/s, which seems awfully low.

Michael Rose (@Xorlev )
Senior Platform Engineer, FullContact 
mich...@fullcontact.com

On Mon, Sep 22, 2014 at 8:05 PM, Kushan Maskey <
kushan.mas...@mmillerassociates.com> wrote:

> I am trying to load 20 M records into Cassandra database through
> Kafka-Storm. I am able to post all the data in 5 mins into Kafka. But
> reading it from storm and inserting into Cassandra, Couch and Solr is kind
> of very slow. It has been running for past 5 hours and so far only 2
> Million records.
>
> How do I make the storm perform faster? Coz in this pace it will take
> couple of days to load all the data.
>
> --
> Kushan Maskey
>
>

Re: Storm performing very slow

[Kushan Maskey]

Here is my storm config.


storm.config.setMaxTaskParallelism=4

storm.config.setNumWorkers=20

storm.config.setMaxSpoutPending=5000

storm.config.numAckers=1000


I am guessing I need to increase the maxTaskParallelism more. IF that is
the case how much would you suggest? Any  help will be highly appreciated.


Thanks.

--
Kushan Maskey
817.403.7500

On Mon, Sep 22, 2014 at 9:20 PM, Michael Rose 
wrote:

> Storm is not your bottleneck. Check your Storm code to 1) ensure you're
> parallelizing your writes and 2) you're batching writes to your external
> resources if possible. Some quick napkin math shows you only doing 110
> writes/s, which seems awfully low.
>
> Michael Rose (@Xorlev )
> Senior Platform Engineer, FullContact 
> mich...@fullcontact.com
>
> On Mon, Sep 22, 2014 at 8:05 PM, Kushan Maskey <
> kushan.mas...@mmillerassociates.com> wrote:
>
>> I am trying to load 20 M records into Cassandra database through
>> Kafka-Storm. I am able to post all the data in 5 mins into Kafka. But
>> reading it from storm and inserting into Cassandra, Couch and Solr is kind
>> of very slow. It has been running for past 5 hours and so far only 2
>> Million records.
>>
>> How do I make the storm perform faster? Coz in this pace it will take
>> couple of days to load all the data.
>>
>> --
>> Kushan Maskey
>>
>>
>

Re: Storm performing very slow

[Kushan Maskey]

Below is my Topology configuration and Topology status bases on the
configuration. Can anyone help me how to optimize the storm for faster
process of the 20 Million data?

Topology statsWindowEmittedTransferredComplete latency (ms)AckedFailed10m 0s

11142011142047305.48828610003h 0m 0s

11142011142047305.48828610001d 0h 0m 0s

11142011142047305.4882861000All time

11142011142047305.4882861000

Topology ConfigurationKeyValuedev.zookeeper.path/tmp/dev-storm-zookeeper
drpc.childopts-Xmx768mdrpc.invocations.port3773drpc.port3772drpc.queue.size
128drpc.request.timeout.secs600drpc.worker.threads64java.library.path
/usr/local/lib:/opt/local/lib:/usr/liblogviewer.appender.nameA1
logviewer.childopts-Xmx128mlogviewer.port8000nimbus.childopts-Xmx1024m
nimbus.cleanup.inbox.freq.secs600nimbus.file.copy.expiration.secs600
nimbus.hostmystormservernimbus.inbox.jar.expiration.secs3600
nimbus.monitor.freq.secs10nimbus.reassigntruenimbus.supervisor.timeout.secs
60nimbus.task.launch.secs120nimbus.task.timeout.secs30
nimbus.thrift.max_buffer_size1048576nimbus.thrift.port6627
nimbus.topology.validatorbacktype.storm.nimbus.DefaultTopologyValidator
storm.cluster.modedistributedstorm.config.properties[object Object]storm.id
CEXPStormTopology-1-1411442050storm.local.dir/data/disk00/storm/localdir
storm.local.mode.zmqfalsestorm.messaging.netty.buffer_size5242880
storm.messaging.netty.client_worker_threads1
storm.messaging.netty.flush.check.interval.ms10
storm.messaging.netty.max_retries30storm.messaging.netty.max_wait_ms1000
storm.messaging.netty.min_wait_ms100
storm.messaging.netty.server_worker_threads1
storm.messaging.netty.transfer.batch.size262144storm.messaging.transport
backtype.storm.messaging.netty.Contextstorm.thrift.transport
backtype.storm.security.auth.SimpleTransportPlugin
storm.zookeeper.connection.timeout15000storm.zookeeper.port2181
storm.zookeeper.retry.interval1000
storm.zookeeper.retry.intervalceiling.millis3storm.zookeeper.retry.times
5storm.zookeeper.root/stormstorm.zookeeper.serversmystormserver
storm.zookeeper.session.timeout2supervisor.childopts-Xmx256m
supervisor.enabletruesupervisor.heartbeat.frequency.secs5
supervisor.monitor.frequency.secs3supervisor.slots.ports
6700,6701,6702,6703,6704,6705,6706,6707,6708,6709,6710,6711,6712,6713,6714,6715,6716,6717,6718,6719,6720,6721,6722,6723,6724,6725,6726,6727,6728
supervisor.worker.start.timeout.secs120supervisor.worker.timeout.secs30
task.heartbeat.frequency.secs3task.refresh.poll.secs10
topology.acker.executors1000topology.builtin.metrics.bucket.size.secs60
topology.debugtruetopology.disruptor.wait.strategy
com.lmax.disruptor.BlockingWaitStrategytopology.enable.message.timeoutstrue
topology.error.throttle.interval.secs10topology.executor.receive.buffer.size
65536topology.executor.send.buffer.size65536
topology.fall.back.on.java.serializationtruetopology.kryo.decorators
topology.kryo.factorybacktype.storm.serialization.DefaultKryoFactory
topology.kryo.register[object Object]topology.max.error.report.per.interval5
topology.max.spout.pending5000topology.max.task.parallelism100
topology.message.timeout.secs60topology.multilang.serializer
backtype.storm.multilang.JsonSerializertopology.nameCEXPStormTopology
topology.receiver.buffer.size8topology.skip.missing.kryo.registrationsfalse
topology.sleep.spout.wait.strategy.time.ms1topology.spout.wait.strategy
backtype.storm.spout.SleepSpoutWaitStrategy
topology.state.synchronization.timeout.secs60topology.stats.sample.rate0.05
topology.taskstopology.tick.tuple.freq.secstopology.transfer.buffer.size32
topology.trident.batch.emit.interval.millis500topology.tuple.serializer
backtype.storm.serialization.types.ListDelegateSerializer
topology.worker.childoptstopology.worker.receiver.thread.count1
topology.worker.shared.thread.pool.size4topology.workers20
transactional.zookeeper.porttransactional.zookeeper.root/transactional
transactional.zookeeper.serversui.childopts-Xmx768mui.port8080
worker.childopts-Xmx1024mworker.heartbeat.frequency.secs1zmq.hwm0
zmq.linger.millis5000zmq.threads1


--
Kushan Maskey
817.403.7500

On Mon, Sep 22, 2014 at 9:25 PM, Kushan Maskey <
kushan.mas...@mmillerassociates.com> wrote:

> Here is my storm config.
>
>
> storm.config.setMaxTaskParallelism=4
>
> storm.config.setNumWorkers=20
>
> storm.config.setMaxSpoutPending=5000
>
> storm.config.numAckers=1000
>
>
> I am guessing I need to increase the maxTaskParallelism more. IF that is
> the case how much would you suggest? Any  help will be highly appreciated.
>
>
> Thanks.
>
> --
> Kushan Maskey
> 817.403.7500
>
> On Mon, Sep 22, 2014 at 9:20 PM, Michael Rose 
> wrote:
>
>> Storm is not your bottleneck.

Re: Storm performing very slow

[Tom Brown]

The screen shows a complete Latency of 47 seconds. That is really high. Is
there a screen that shows the performance/capacity of each bolt?

--Tom

On Mon, Sep 22, 2014 at 9:27 PM, Kushan Maskey <
kushan.mas...@mmillerassociates.com> wrote:

> Below is my Topology configuration and Topology status bases on the
> configuration. Can anyone help me how to optimize the storm for faster
> process of the 20 Million data?
>
> Topology statsWindowEmittedTransferredComplete latency (ms)AckedFailed10m
> 0s
> 
> 11142011142047305.48828610003h 0m 0s
> 
> 11142011142047305.48828610001d 0h 0m 0s
> 
> 11142011142047305.4882861000All time
> 
> 11142011142047305.4882861000
>
> Topology ConfigurationKeyValuedev.zookeeper.path/tmp/dev-storm-zookeeper
> drpc.childopts-Xmx768mdrpc.invocations.port3773drpc.port3772
> drpc.queue.size128drpc.request.timeout.secs600drpc.worker.threads64
> java.library.path/usr/local/lib:/opt/local/lib:/usr/lib
> logviewer.appender.nameA1logviewer.childopts-Xmx128mlogviewer.port8000
> nimbus.childopts-Xmx1024mnimbus.cleanup.inbox.freq.secs600
> nimbus.file.copy.expiration.secs600nimbus.hostmystormserver
> nimbus.inbox.jar.expiration.secs3600nimbus.monitor.freq.secs10
> nimbus.reassigntruenimbus.supervisor.timeout.secs60nimbus.task.launch.secs
> 120nimbus.task.timeout.secs30nimbus.thrift.max_buffer_size1048576
> nimbus.thrift.port6627nimbus.topology.validator
> backtype.storm.nimbus.DefaultTopologyValidatorstorm.cluster.mode
> distributedstorm.config.properties[object Object]storm.id
> CEXPStormTopology-1-1411442050storm.local.dir/data/disk00/storm/localdir
> storm.local.mode.zmqfalsestorm.messaging.netty.buffer_size5242880
> storm.messaging.netty.client_worker_threads1
> storm.messaging.netty.flush.check.interval.ms10
> storm.messaging.netty.max_retries30storm.messaging.netty.max_wait_ms1000
> storm.messaging.netty.min_wait_ms100
> storm.messaging.netty.server_worker_threads1
> storm.messaging.netty.transfer.batch.size262144storm.messaging.transport
> backtype.storm.messaging.netty.Contextstorm.thrift.transport
> backtype.storm.security.auth.SimpleTransportPlugin
> storm.zookeeper.connection.timeout15000storm.zookeeper.port2181
> storm.zookeeper.retry.interval1000
> storm.zookeeper.retry.intervalceiling.millis3
> storm.zookeeper.retry.times5storm.zookeeper.root/storm
> storm.zookeeper.serversmystormserverstorm.zookeeper.session.timeout2
> supervisor.childopts-Xmx256msupervisor.enabletrue
> supervisor.heartbeat.frequency.secs5supervisor.monitor.frequency.secs3
> supervisor.slots.ports
> 6700,6701,6702,6703,6704,6705,6706,6707,6708,6709,6710,6711,6712,6713,6714,6715,6716,6717,6718,6719,6720,6721,6722,6723,6724,6725,6726,6727,6728
> supervisor.worker.start.timeout.secs120supervisor.worker.timeout.secs30
> task.heartbeat.frequency.secs3task.refresh.poll.secs10
> topology.acker.executors1000topology.builtin.metrics.bucket.size.secs60
> topology.debugtruetopology.disruptor.wait.strategy
> com.lmax.disruptor.BlockingWaitStrategytopology.enable.message.timeouts
> truetopology.error.throttle.interval.secs10
> topology.executor.receive.buffer.size65536
> topology.executor.send.buffer.size65536
> topology.fall.back.on.java.serializationtruetopology.kryo.decorators
> topology.kryo.factorybacktype.storm.serialization.DefaultKryoFactory
> topology.kryo.register[object Object]
> topology.max.error.report.per.interval5topology.max.spout.pending5000
> topology.max.task.parallelism100topology.message.timeout.secs60
> topology.multilang.serializerbacktype.storm.multilang.JsonSerializer
> topology.nameCEXPStormTopologytopology.receiver.buffer.size8
> topology.skip.missing.kryo.registrationsfalse
> topology.sleep.spout.wait.strategy.time.ms1topology.spout.wait.strategy
> backtype.storm.spout.SleepSpoutWaitStrategy
> topology.state.synchronization.timeout.secs60topology.stats.sample.rate
> 0.05topology.taskstopology.tick.tuple.freq.secs
> topology.transfer.buffer.size32topology.trident.batch.emit.interval.millis
> 500topology.tuple.serializer
> backtype.storm.serialization.types.ListDelegateSerializer
> topology.worker.childoptstopology.worker.receiver.thread.count1
> topology.worker.shared.thread.pool.size4topology.workers20
> transactional.zookeeper.porttransactional.zookeeper.root/transactional
> transactional.zookeeper.serversui.childopts-Xmx768mui.port8080
> worker.childopts-Xmx1024mworker.heartbeat.frequency.secs1zmq.hwm0
> zmq.linger.millis5000zmq.threads1
>
>
> --
> Kushan Maskey
> 817.403.7500
>
> On Mon, Sep 22, 2014 at 9:25 PM, Kushan Maskey <
> kushan.mas...@mmillerassociates.com> wrote:
>
>> Here is my storm config.
>>
>>
>> storm.config.setMaxTaskParallel

Re: Storm performing very slow

[Kushan Maskey]

That is what is causing the storm to perform very slow data read and
process. And I am not sure what is causing it to be that slow.

--
Kushan Maskey
817.403.7500

On Mon, Sep 22, 2014 at 10:30 PM, Tom Brown  wrote:

> The screen shows a complete Latency of 47 seconds. That is really high. Is
> there a screen that shows the performance/capacity of each bolt?
>
> --Tom
>
> On Mon, Sep 22, 2014 at 9:27 PM, Kushan Maskey <
> kushan.mas...@mmillerassociates.com> wrote:
>
>> Below is my Topology configuration and Topology status bases on the
>> configuration. Can anyone help me how to optimize the storm for faster
>> process of the 20 Million data?
>>
>> Topology statsWindowEmittedTransferredComplete latency (ms)AckedFailed10m
>> 0s
>> 
>> 11142011142047305.48828610003h 0m 0s
>> 
>> 11142011142047305.48828610001d 0h 0m 0s
>> 
>> 11142011142047305.4882861000All time
>> 
>> 11142011142047305.4882861000
>>
>> Topology ConfigurationKeyValuedev.zookeeper.path/tmp/dev-storm-zookeeper
>> drpc.childopts-Xmx768mdrpc.invocations.port3773drpc.port3772
>> drpc.queue.size128drpc.request.timeout.secs600drpc.worker.threads64
>> java.library.path/usr/local/lib:/opt/local/lib:/usr/lib
>> logviewer.appender.nameA1logviewer.childopts-Xmx128mlogviewer.port8000
>> nimbus.childopts-Xmx1024mnimbus.cleanup.inbox.freq.secs600
>> nimbus.file.copy.expiration.secs600nimbus.hostmystormserver
>> nimbus.inbox.jar.expiration.secs3600nimbus.monitor.freq.secs10
>> nimbus.reassigntruenimbus.supervisor.timeout.secs60
>> nimbus.task.launch.secs120nimbus.task.timeout.secs30
>> nimbus.thrift.max_buffer_size1048576nimbus.thrift.port6627
>> nimbus.topology.validatorbacktype.storm.nimbus.DefaultTopologyValidator
>> storm.cluster.modedistributedstorm.config.properties[object Object]
>> storm.idCEXPStormTopology-1-1411442050storm.local.dir
>> /data/disk00/storm/localdirstorm.local.mode.zmqfalse
>> storm.messaging.netty.buffer_size5242880
>> storm.messaging.netty.client_worker_threads1
>> storm.messaging.netty.flush.check.interval.ms10
>> storm.messaging.netty.max_retries30storm.messaging.netty.max_wait_ms1000
>> storm.messaging.netty.min_wait_ms100
>> storm.messaging.netty.server_worker_threads1
>> storm.messaging.netty.transfer.batch.size262144storm.messaging.transport
>> backtype.storm.messaging.netty.Contextstorm.thrift.transport
>> backtype.storm.security.auth.SimpleTransportPlugin
>> storm.zookeeper.connection.timeout15000storm.zookeeper.port2181
>> storm.zookeeper.retry.interval1000
>> storm.zookeeper.retry.intervalceiling.millis3
>> storm.zookeeper.retry.times5storm.zookeeper.root/storm
>> storm.zookeeper.serversmystormserverstorm.zookeeper.session.timeout2
>> supervisor.childopts-Xmx256msupervisor.enabletrue
>> supervisor.heartbeat.frequency.secs5supervisor.monitor.frequency.secs3
>> supervisor.slots.ports
>> 6700,6701,6702,6703,6704,6705,6706,6707,6708,6709,6710,6711,6712,6713,6714,6715,6716,6717,6718,6719,6720,6721,6722,6723,6724,6725,6726,6727,6728
>> supervisor.worker.start.timeout.secs120supervisor.worker.timeout.secs30
>> task.heartbeat.frequency.secs3task.refresh.poll.secs10
>> topology.acker.executors1000topology.builtin.metrics.bucket.size.secs60
>> topology.debugtruetopology.disruptor.wait.strategy
>> com.lmax.disruptor.BlockingWaitStrategytopology.enable.message.timeouts
>> truetopology.error.throttle.interval.secs10
>> topology.executor.receive.buffer.size65536
>> topology.executor.send.buffer.size65536
>> topology.fall.back.on.java.serializationtruetopology.kryo.decorators
>> topology.kryo.factorybacktype.storm.serialization.DefaultKryoFactory
>> topology.kryo.register[object Object]
>> topology.max.error.report.per.interval5topology.max.spout.pending5000
>> topology.max.task.parallelism100topology.message.timeout.secs60
>> topology.multilang.serializerbacktype.storm.multilang.JsonSerializer
>> topology.nameCEXPStormTopologytopology.receiver.buffer.size8
>> topology.skip.missing.kryo.registrationsfalse
>> topology.sleep.spout.wait.strategy.time.ms1topology.spout.wait.strategy
>> backtype.storm.spout.SleepSpoutWaitStrategy
>> topology.state.synchronization.timeout.secs60topology.stats.sample.rate
>> 0.05topology.taskstopology.tick.tuple.freq.secs
>> topology.transfer.buffer.size32
>> topology.trident.batch.emit.interval.millis500topology.tuple.serializer
>> backtype.storm.serialization.types.ListDelegateSerializer
>> topology.worker.childoptstopology.worker.receiver.thread.count1
>> topology.worker.shared.thread.pool.size4topology.workers20
>> transactional.zookeeper.porttransactional.zookeeper.root/transactional
>> transactional.zookeeper.serversui.childopts-Xmx768mui.port8080
>> wo

Re: Apache Storm Graduation to a TLP

[Vikas Agarwal]

Great!

On Tue, Sep 23, 2014 at 2:46 AM, P. Taylor Goetz  wrote:

> I’m pleased to announce that Apache Storm has graduated to a Top-Level
> Project (TLP), and I’d like to thank everyone in the Storm community for
> your contributions and help in achieving this important milestone.
>
> As part of the graduation process, a number of infrastructure changes have
> taken place:
>
> *New website url:* http://storm.apache.org
>
> *New git repo urls:*
>
> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>
> g...@github.com:apache/storm.git
> -or-
> https://github.com/apache/storm.git (for github pull requests)
>
> *Mailing Lists:*
> If you are already subscribed, you’re subscription has been migrated. New
> messages should be sent to the new address:
>
> [list]@storm.apache.org
>
> This includes any subscribe/unsubscribe requests.
>
> Note: The mail-archives.apache.org site will not reflect these changes
> until October 1.
>
>
> Most of these changes have already occurred and are seamless. Please
> update your git remotes and address books accordingly.
>
> - Taylor
>



-- 
Regards,
Vikas Agarwal
91 – 9928301411

InfoObjects, Inc.
Execution Matters
http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
+1 (408) 988-2000 Work
+1 (408) 716-2726 Fax

Re: Apache Storm Graduation to a TLP

[Cheng Chen]

great news!

On Mon, Sep 22, 2014 at 9:33 PM, Vikas Agarwal 
wrote:

> Great!
>
> On Tue, Sep 23, 2014 at 2:46 AM, P. Taylor Goetz 
> wrote:
>
>> I’m pleased to announce that Apache Storm has graduated to a Top-Level
>> Project (TLP), and I’d like to thank everyone in the Storm community for
>> your contributions and help in achieving this important milestone.
>>
>> As part of the graduation process, a number of infrastructure changes
>> have taken place:
>>
>> *New website url:* http://storm.apache.org
>>
>> *New git repo urls:*
>>
>> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>>
>> g...@github.com:apache/storm.git
>> -or-
>> https://github.com/apache/storm.git (for github pull requests)
>>
>> *Mailing Lists:*
>> If you are already subscribed, you’re subscription has been migrated. New
>> messages should be sent to the new address:
>>
>> [list]@storm.apache.org
>>
>> This includes any subscribe/unsubscribe requests.
>>
>> Note: The mail-archives.apache.org site will not reflect these changes
>> until October 1.
>>
>>
>> Most of these changes have already occurred and are seamless. Please
>> update your git remotes and address books accordingly.
>>
>> - Taylor
>>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>

Re: Apache Storm Graduation to a TLP

[padma priya chitturi]

Good news !!! Congrats

On Tue, Sep 23, 2014 at 10:04 AM, Cheng Chen  wrote:

> great news!
>
> On Mon, Sep 22, 2014 at 9:33 PM, Vikas Agarwal 
> wrote:
>
>> Great!
>>
>> On Tue, Sep 23, 2014 at 2:46 AM, P. Taylor Goetz 
>> wrote:
>>
>>> I’m pleased to announce that Apache Storm has graduated to a Top-Level
>>> Project (TLP), and I’d like to thank everyone in the Storm community for
>>> your contributions and help in achieving this important milestone.
>>>
>>> As part of the graduation process, a number of infrastructure changes
>>> have taken place:
>>>
>>> *New website url:* http://storm.apache.org
>>>
>>> *New git repo urls:*
>>>
>>> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
>>>
>>> g...@github.com:apache/storm.git
>>> -or-
>>> https://github.com/apache/storm.git (for github pull requests)
>>>
>>> *Mailing Lists:*
>>> If you are already subscribed, you’re subscription has been migrated.
>>> New messages should be sent to the new address:
>>>
>>> [list]@storm.apache.org
>>>
>>> This includes any subscribe/unsubscribe requests.
>>>
>>> Note: The mail-archives.apache.org site will not reflect these changes
>>> until October 1.
>>>
>>>
>>> Most of these changes have already occurred and are seamless. Please
>>> update your git remotes and address books accordingly.
>>>
>>> - Taylor
>>>
>>
>>
>>
>> --
>> Regards,
>> Vikas Agarwal
>> 91 – 9928301411
>>
>> InfoObjects, Inc.
>> Execution Matters
>> http://www.infoobjects.com
>> 2041 Mission College Boulevard, #280
>> Santa Clara, CA 95054
>> +1 (408) 988-2000 Work
>> +1 (408) 716-2726 Fax
>>
>>
>

Re: Apache Storm Graduation to a TLP

[James Xu]

Great News!

On 2014年9月23日, at 下午1:32, padma priya chitturi  wrote:

> Good news !!! Congrats
> 
> On Tue, Sep 23, 2014 at 10:04 AM, Cheng Chen  wrote:
> great news!
> 
> On Mon, Sep 22, 2014 at 9:33 PM, Vikas Agarwal  wrote:
> Great!
> 
> On Tue, Sep 23, 2014 at 2:46 AM, P. Taylor Goetz  wrote:
> I’m pleased to announce that Apache Storm has graduated to a Top-Level 
> Project (TLP), and I’d like to thank everyone in the Storm community for your 
> contributions and help in achieving this important milestone.
> 
> As part of the graduation process, a number of infrastructure changes have 
> taken place:
> 
> New website url: http://storm.apache.org
> 
> New git repo urls:
> 
> https://git-wip-us.apache.org/repos/asf/storm.git (for committer push)
> 
> g...@github.com:apache/storm.git
> -or-
> https://github.com/apache/storm.git (for github pull requests)
> 
> Mailing Lists:
> If you are already subscribed, you’re subscription has been migrated. New 
> messages should be sent to the new address:
> 
> [list]@storm.apache.org
> 
> This includes any subscribe/unsubscribe requests.
> 
> Note: The mail-archives.apache.org site will not reflect these changes until 
> October 1.
> 
> 
> Most of these changes have already occurred and are seamless. Please update 
> your git remotes and address books accordingly.
> 
> - Taylor
> 
> 
> 
> -- 
> Regards,
> Vikas Agarwal
> 91 – 9928301411
> 
> InfoObjects, Inc. 
> Execution Matters
> http://www.infoobjects.com 
> 2041 Mission College Boulevard, #280 
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
> 
> 
>