[
https://issues.apache.org/jira/browse/BOOKKEEPER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763049#comment-13763049
]
Flavio Junqueira commented on BOOKKEEPER-675:
---------------------------------------------
If the log message is not fulfilling its role, then we are possibly not doing
logging right in that part of the code. I don't think it is a big deal and it
certainly doesn't make sense to hold 4.2.2 because of this issue. +1, ship it.
> 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
>
> Attachments:
> 0001-BOOKKEEPER-675-Log-noise-fixup-before-cutting-4.2.2.patch,
> 0001-BOOKKEEPER-675-Log-noise-fixup-before-cutting-4.2.2.patch,
> 0001-BOOKKEEPER-675-Log-noise-fixup-trunk.patch,
> 0001-BOOKKEEPER-675-Log-noise-fixup-trunk.patch
>
>
> 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
