One more following question about __acker bolt. Even though I created un-anchored topology ( http://storm.apache.org/releases/current/Guaranteeing-message-processing.html), it still created __acker bolt in each worker.
Are there reasons? Thanks, Junguk 2016-07-05 21:45 GMT-04:00 Junguk Cho <[email protected]>: > Hi, > > Thank you for reply. > I checked the code. > > I have some questions. > There is no code for sending data to "central node" by using "emit-like > function". > Who will get the worker level metrics from this SystemBolt? > > It seemed we cannot disable this SystemBolt. > Can we also disable this in storm.yaml? > > > Thanks, > Junguk > > 2016-06-28 9:57 GMT-04:00 Bobby Evans <[email protected]>: > >> Every worker gets a SystemBolt. The bolt does not really process any >> data, it just provides a set of worker level metrics. >> >> https://github.com/apache/storm/blob/master/storm-core/src/jvm/org/apache/storm/metric/SystemBolt.java >> - Bobby >> >> On Monday, June 27, 2016 10:42 AM, Junguk Cho <[email protected]> >> wrote: >> >> >> Hi, >> >> In one worker, by default Storm creates one-executor and >> one-executor-disruptor threads pair. >> >> In detail, it created __system, __acker, and __bolt or __spout. >> I understood __acker and __bolt or __spout, but what is the roles of >> __system and __system-disruptor threads? >> >> >> Another question is a benchmark. >> I found one from Yahoo which they used it for netty vs zeromq test ( >> https://github.com/yahoo/storm-perf-test). >> >> Are there well built benchmark like this to measure storm performances? >> >> Thanks, >> Junguk >> >> >> >> > >
