Re: How to bring a node offline?

kill -9 pid 2014-07-08 唐思成 发件人： jeff saremi 发送时间： 2014-07-08 10:43:25 收件人： user@storm.incubator.apache.org 抄送： 主题： How to bring a node offline? What is the sequence or command to make a node unavailable say for maintenance? This is one of the supervisor nodes of course. thanks

回复：RE: storm 0.9.2-incubating, nimbus is not launching.

Which version did you upgrade from? I try to upgrade 0.9.1 to 0.9.2 , and I encounter the same problem.‍ -- 原始邮件 -- 发件人: 이승진;sweetest...@navercorp.com; 发送时间: 2014年7月1日(星期二) 下午2:10 收件人: useruser@storm.incubator.apache.org; 主题: RE: storm 0.9.2-incubating, nimbus

could assign Topology execute in some supervisor

The Storm has 8 supervisors,i want assign a topology run in 2 superviosrs,and the 2 supercisor only execute the topology. how can i do it? Thanks， Lax

Re: could assign Topology execute in some supervisor

yes, config.setNumWorkers(2); this will run 2 worker processes, usually on 2 separate supervisor machines. On Tue, Jul 8, 2014 at 6:12 AM, chenlax lax...@hotmail.com wrote: The Storm has 8 supervisors,i want assign a topology run in 2 superviosrs,and the 2 supercisor only

RE: could assign Topology execute in some supervisor

i means assign 2 supervisor machines execute a topology,the worker number more than 2.maybe 10 or more. Thanks， Lax Date: Tue, 8 Jul 2014 08:11:30 -0400 Subject: Re: could assign Topology execute in some supervisor From: tomas.mazu...@gmail.com To: user@storm.incubator.apache.org yes,

RE: could assign Topology execute in some supervisor

Does the isolation scheduler suit your needs? https://storm.incubator.apache.org/2013/01/11/storm082-released.html On Jul 8, 2014 8:53 AM, chenlax lax...@hotmail.com wrote: i means assign 2 supervisor machines execute a topology,the worker number more than 2.maybe 10 or more. Thanks， Lax

topology system metrics

Is there a way to get a hold of the topology's system metrics and send it to an external datastore such as dynamoDb ? -- Raphael Hsieh

Re: Kafka trident getting stuck

Try lowering setMaxSpoutPending(10) to a much lower value (like 10). In Trident, setMaxSpoutPending referns to the number of batches, not tuples like in plain Storm. Too high values may cause blockages like the one you describe. On Tuesday, July 8, 2014, Miloš Solujić milos.solu...@gmail.com

Re: topology system metrics

Yes, you can implement your own Storm metrics stream consumer. Take a look at the example LoggingMetricsConsumer that comes bundled with Storm. On Tuesday, July 8, 2014, Raphael Hsieh raffihs...@gmail.com wrote: Is there a way to get a hold of the topology's system metrics and send it to an

Re: Kafka trident getting stuck

Yep. pretty much sure. Via internal kafka-producer.sh same method is used to produce initial messages (before first launch of topology, that got consumed and processed just fine) as for maxSpoutPending first I tried with 10, than removed it (left default value) On Tue, Jul 8, 2014 at 6:31 PM,

Re: Kafka trident getting stuck

Also, you should paste all your worker logs (worker-*.log files). On Tuesday, July 8, 2014, Danijel Schiavuzzi dani...@schiavuzzi.com wrote: I'd double check the Kafka producer to make sure those messages are really getting into the right Kafka topic. Also, try enabling Config.setDebug(true)