[
https://issues.apache.org/jira/browse/BOOKKEEPER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748701#comment-13748701
]
Ivan Kelly commented on BOOKKEEPER-675:
---------------------------------------
[~hustlmsp] But it's ok if it's not there. The problem is if it's different.
Not being there means an old cluster. Being different means corruption. INFO
logs are enabled by default anyhow, so it will show up in the logs. It just
wont trigger monitoring systems.
> Log noise fixup before cutting 4.2.2
> ------------------------------------
>
> 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
