You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/07/02 19:45:20 UTC

[jira] [Commented] (BOOKKEEPER-637) NoSuchEntry exception when reading an entry from a bookie should not print ERROR level message

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

Ivan Kelly commented on BOOKKEEPER-637:
---------------------------------------

Committed as r1499032 to trunk.
                
> NoSuchEntry exception when reading an entry from a bookie should not print ERROR level message
> ----------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-637
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-637
>             Project: Bookkeeper
>          Issue Type: Improvement
>    Affects Versions: 4.2.1, 4.3.0
>            Reporter: Matteo Merli
>            Assignee: Matteo Merli
>            Priority: Trivial
>             Fix For: 4.2.2, 4.3.0
>
>         Attachments: BOOKKEEPER-637.diff
>
>
> The NoSuchEntry is an internal error that is recoverable within the BK client library by issuing a read to a different bookie.
> I think that INFO level should be more appropriate.

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