You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2013/08/23 06:40:53 UTC
[jira] [Commented] (BOOKKEEPER-675) Lack of instanceid message
should be info level, not warn.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748279#comment-13748279 ]
Sijie Guo commented on BOOKKEEPER-675:
--------------------------------------
since instanceid is used for data integrity guarantee, I don't think it is a good idea to change it to info. maybe we could consider how to upgrade an old system to provide instanceid.
> Lack of instanceid message should be info level, not warn.
> ----------------------------------------------------------
>
> Key: BOOKKEEPER-675
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-675
> Project: Bookkeeper
> Issue Type: Wish
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.2, 4.3.0
>
>
> The message isn't a warning, but an information message that tells you that you initiated your cluster before instance ids existed, as such it should be info level so it doesn't show up on monitoring systems.
> WARN org.apache.bookkeeper.bookie.Bookie - INSTANCEID not exists in
> zookeeper. Not considering it for data verification
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira