@storm.incubator.apache.org
user@storm.incubator.apache.orgmailto:user@storm.incubator.apache.org
Cc: d...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
d...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
Subject: Re: High CPU utilization after storm node failover
+ dev
, 2014 at 8:15 PM
To: user@storm.incubator.apache.org user@storm.incubator.apache.org
Cc: d...@storm.incubator.apache.org d...@storm.incubator.apache.org
Subject: Re: High CPU utilization after storm node failover
+ dev@storm
Vinyasa/Srinath,
Anything you can share to make
...@storm.incubator.apache.org d...@storm.incubator.apache.org
Subject: Re: High CPU utilization after storm node failover
+ dev@storm
Vinyasa/Srinath,
Anything you can share to make this reproducible would be very helpful.
I would love to see a network partition simulation framework for Storm
along
[Storm Version: 0.9.2-incubating]
Hello,
I am trying to test failover scenarios with my storm cluster. The following
are the details of the cluster:
* 4 nodes
* Each node with 2 slots
* Topology with around 600 spouts and bolts
* Num. Workers for the topology = 4
I am running a test that
I have seen this behaviour too using 0.9.2-incubating.
The failover works better when there is a redundant node available. Maybe 1
slot per node is the best approach.
Eager to know if there are any steps to further diagnose.
On Wed, Aug 6, 2014 at 5:43 AM, Vinay Pothnis vinay.poth...@gmail.com
+ dev@storm
Vinyasa/Srinath,
Anything you can share to make this reproducible would be very helpful.
I would love to see a network partition simulation framework for Storm along
the lines of what Kyle Kingsbury has done with Jepsen [1]. It basically sets up
a virtual cluster then simulates
