You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:05 UTC

[jira] [Updated] (ZOOKEEPER-715) add better reporting for initLimit being reached

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han updated ZOOKEEPER-715:
----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> add better reporting for initLimit being reached
> ------------------------------------------------
>
>                 Key: ZOOKEEPER-715
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-715
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.2.2
>            Reporter: Patrick Hunt
>             Fix For: 3.5.4, 3.6.0
>
>
> when the initLimit is reached (sending zk database to follower) we don't print out very useful log information.
> we need to add details on when the snap is read, when the new snap is written, and the start/end of the transfer to follower. start/end should include useful logging in the case that initLimit is reached and the operation fails.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)