Yes, that should work too. 2017-07-21 13:35 GMT+02:00 I PVP <i...@hotmail.com>:
> Would defining it for each topology with the following code be also a > option or is there any disadvantage of doing it this way? > -- > org.apache.storm.Config conf = new Config(); > …. > conf.put(Config.TOPOLOGY_SLEEP_SPOUT_WAIT_STRATEGY_TIME_MS, 3000); > -- > > best, > IPVP > > > On July 21, 2017 at 4:21:52 AM, Stig Rohde Døssing (s...@apache.org) > wrote: > > When a call to nextTuple on the spout doesn't emit any tuples, the spout > executor will sleep for a bit. The duration is set here > https://github.com/apache/storm/blob/e38f936077ea9b3ba5cd568 > b69335e0aac8369dd/conf/defaults.yaml#L247, you could increase it if you > want. > > 2017-07-21 <20%2017%2007%2021> 3:18 GMT+02:00 I PVP <i...@hotmail.com>: > >> I am experiencing very High CPU usage with storm-kafka spout even when >> idle for hours. >> >> I changed all my Kafka Spouts to the new >> org.apache.storm.kafka.spout.KafkaSpout >> but the issue continues. >> >> How to tune it ? >> Is there something like a Utils.sleep for KafkaSpout? >> >> Thanks >> >> IP VP >> > >
