You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/03/18 18:44:27 UTC

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

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.3.1


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-715:
-----------------------------------

    Fix Version/s: 3.4.0

> 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.3.1, 3.4.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated ZOOKEEPER-715:
------------------------------------

    Fix Version/s:     (was: 3.3.1)

moving this to 3.4 release. not a regression!

> 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.4.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.