回复:回复:InpoolUsage & InpoolBuffers inconsistence

2018-09-18 Thread Zhijiang(wangzhijiang999)
3. I suggest you upgrading the version to 1.5 or above. The checkpoint process may be faster than the current version. Best, Zhijiang -- 发件人:aitozi 发送时间:2018年9月18日(星期二) 14:53 收件人:user 主 题:Re: 回复:InpoolUsage & InpoolBuffers inconsist

Re: 回复:InpoolUsage & InpoolBuffers inconsistence

2018-09-17 Thread aitozi
Hi,Zhijiang Thanks for your reply. But i still have little question. Let me make my debug process more clearly。I log in PartitionRequestQueue to ensure the action of write a barrier and the callback of writeAndFlush is almost at the same time. (Which is done by check the buffer to be sent whether

回复:InpoolUsage & InpoolBuffers inconsistence

2018-09-17 Thread Zhijiang(wangzhijiang999)
Hi, The inpoolQueueLength indicates hown many buffers are received and queued. But if the buffers in the queue are the events (like barrier), it will not be calculated in the inpoolUsage. So in your case it may be normal for these two metrics. If you monitored that the autoread=false in downstr