client use high cpu which caused by delayedFetch operation immediately return

Hi all, we found our consumer have high cpu load in our product enviroment，as we know，fetch.min.bytes and fetch.wait.ma x.ms will affect the frequency of consumer’s return， so we adjust them to very big so that broker is very hard to satisfy it. then we foun

Re: client use high cpu which caused by delayedFetch operation immediately return

Can you check if you have KAFKA-3003 when you run the code? On Sat, Oct 8, 2016 at 12:52 AM, Kafka wrote: > Hi all, > we found our consumer have high cpu load in our product > enviroment，as we know，fetch.min.bytes and fetch.wait.ma < > http://fetch.wait.ma/>x.ms will affect the frequency

Re: client use high cpu which caused by delayedFetch operation immediately return

Thanks. I patch it, and everything goes ok. > 在 2016年10月9日，下午12:39，Becket Qin 写道： > > Can you check if you have KAFKA-3003 when you run the code? > > On Sat, Oct 8, 2016 at 12:52 AM, Kafka wrote: > >> Hi all, >>we found our consumer have high cpu load in our product >> enviroment，as we

Re: client use high cpu which caused by delayedFetch operation immediately return

Glad to know :) On Tue, Oct 18, 2016 at 1:24 AM, Json Tu wrote: > Thanks. I patch it, and everything goes ok. > > 在 2016年10月9日，下午12:39，Becket Qin 写道： > > > > Can you check if you have KAFKA-3003 when you run the code? > > > > On Sat, Oct 8, 2016 at 12:52 AM, Kafka wrote: > > > >> Hi all, > >>