Hello Sam, It is a known issue that should have been fixed in 2.0, the correlated fix has also been cherry-picked to the 1.1.1 bug fix release as well:
https://github.com/apache/kafka/pull/5277 Guozhang On Wed, Jul 11, 2018 at 11:42 AM, Sam Lendle <slen...@pandora.com> wrote: > Hello! > > Using kafka-streams 1.1.0, I noticed when I sum the process rate metric > for a given processor node, the rate is many times higher than the number > of incoming messages. Digging further, it looks like the rate metric > associated with each thread in a given application instance is always the > same, and if I average by instance and then sum the rates, I recover the > incoming message rate. So it looks like the rate metric for each stream > thread is actually the reporting the rate for all threads on the instance. > > Is this a known issue, or am I misusing the metric? I’m not sure if this > affects other metrics, but it does look like the average latency metric is > identical for all threads on the same instance, so I suspect it does. > > Thanks, > Sam > -- -- Guozhang
