zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-715) add better reporting for initLimit being reached
Date Wed, 22 May 2019 03:26:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845459#comment-16845459
] 

Richard Yu commented on ZOOKEEPER-715:
--------------------------------------

Seeing that this is pretty old, would it still be relevant to the current version of zookeeper?

 

> 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
>            Priority: Major
>             Fix For: 3.6.0, 3.5.6
>
>
> 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
(v7.6.3#76005)

Mime
View raw message