回复：回复：InpoolUsage & InpoolBuffers inconsistence

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年9月18日(星期二) 12:59 > 收件人：user < > user@.apache > > > 主　题：Re: InpoolUsage & InpoolBuffers inconsistence > > And my doubt for that comes from the debug of problem of checkpoint > expiration. > I encountered the checkpoint expiration with no

回复：InpoolUsage & InpoolBuffers inconsistence

%, there may be a lot of buffers queued in front of barrier, so the checkpoint may expire as you said. Best, Zhijiang -- 发件人：aitozi 发送时间：2018年9月18日(星期二) 12:59 收件人：user 主　题：Re: InpoolUsage & InpoolBuffers inconsistence And my d

Re: InpoolUsage & InpoolBuffers inconsistence

And my doubt for that comes from the debug of problem of checkpoint expiration. I encountered the checkpoint expiration with no backpressure shown in web ui. But after i add many log, i found that the barrier send to the downstream, And the downstream may be set to autoread = false , and block the

InpoolUsage & InpoolBuffers inconsistence

Hi, I found that these two metric is inconsistent, the inpoolQueueLength is positive, but the inpoolUsage is always zero. Is this a bug? cc @Chesnay Schepler -- Sent from: http://apac