[
https://issues.apache.org/jira/browse/BOOKKEEPER-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006602#comment-16006602
]
ASF GitHub Bot commented on BOOKKEEPER-1057:
--------------------------------------------
Github user eolivelli commented on the issue:
https://github.com/apache/bookkeeper/pull/145
@jvrao I see your point.
In order to achieve this goal in my company we use error collectors which
gather error streams from the various machines (using Kafka/ElasticSearch and
so on). But without "parsing" textual log messages, which can change from
version to version, our apps signal errors in a more structured format.
We cannot use this method for error generated but third party libs, and we
only log exceptions with some kind of "context".
> Do not log error message after read failure in PendingReadOp
> ------------------------------------------------------------
>
> Key: BOOKKEEPER-1057
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1057
> Project: Bookkeeper
> Issue Type: Task
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Trivial
> Fix For: 4.5.0
>
>
> In {{PendingReadOp}}, there is an error message that is printed each time a
> read on a specific bookie is failing:
> {noformat}
> LOG.error("Read of ledger entry failed: L{} E{}-E{}, Heard from {}. First
> unread entry is {}",
> new Object[] { lh.getId(), startEntryId, endEntryId, heardFromHosts,
> firstUnread });
> {noformat}
> This message is getting printed each time a ledger is recovered and there is
> no error, since the ledger recovery logic is to keep reading and incrementing
> the entryId until a NoEntry error is received.
> This log message should be set at debug level.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
