You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Fangmin Lv (Jira)" <ji...@apache.org> on 2020/01/07 19:40:00 UTC
[jira] [Resolved] (ZOOKEEPER-3656) SyncRequestProcessor doesn't
update lastFlushTime correctly on observers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fangmin Lv resolved ZOOKEEPER-3656.
-----------------------------------
Fix Version/s: 3.7.0
Resolution: Fixed
Issue resolved by pull request 1189
[https://github.com/apache/zookeeper/pull/1189]
> SyncRequestProcessor doesn't update lastFlushTime correctly on observers
> ------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3656
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3656
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Eric Hammerle
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This issues was introduced in [ZOOKEEPER-3311|https://github.com/apache/zookeeper/pull/851]. The lastFlushTime used to decide the batch window is not updated correctly for the observer case when the nextProcessor is always be null.
> This can cause observers to fall behind and their sync queue to grow indefinitely.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)