[
https://issues.apache.org/jira/browse/KAFKA-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198055#comment-15198055
]
Scott Reynolds edited comment on KAFKA-3413 at 3/16/16 8:11 PM:
----------------------------------------------------------------
{quote}This is an error due to the severe implications - on a replica, this
will cause a re-replication of an entire partition. Sysadmins will want to know
that their network is about to get really really busy, so this is logged at a
level where they are likely to catch it.{quote}
hmm ok. We do not get it frequently only when we are replacing and reassigning
topics.
Just it isn't an Error. There is nothing wrong.
{quote}a level where they are likely to catch it.{quote}
hmm maybe. Feels bad though doesn't.
In general, my team sets off pages on all Errors but we can adjust that if it
is just us facing this. Just smells a bit.
was (Author: scottreynolds):
>This is an error due to the severe implications - on a replica, this will
>cause a re-replication of an entire partition. Sysadmins will want to know
>that their network is about to get really really busy, so this is logged at a
>level where they are likely to catch it.
hmm ok. We do not get it frequently only when we are replacing and reassigning
topics.
Just it isn't an Error. There is nothing wrong.
>a level where they are likely to catch it.
hmm maybe. Feels bad though doesn't.
In general, my team sets off pages on all Errors but we can adjust that if it
is just us facing this. Just smells a bit.
> Load Error Message should be a Warning
> --------------------------------------
>
> Key: KAFKA-3413
> URL: https://issues.apache.org/jira/browse/KAFKA-3413
> Project: Kafka
> Issue Type: Improvement
> Components: consumer, offset manager
> Affects Versions: 0.9.0.0, 0.9.0.1
> Reporter: Scott Reynolds
> Assignee: Neha Narkhede
>
> There is a Error message from AbstractReplicaFetcherThread that isn't really
> an error.
> Each implementation
> of this thread can logs out when an error or fatal error occurs.
> ReplicaFetcherThread, has both warn, error and fatal in the
> handleOffsetOutOfRange method.
> ConsumerFetcherThread seems to reset itself without logging out an error.
> Seems that the Reset message isn't shouldn't be an error level as it
> doesn't indicate any real error.
> This patch makes it a warning:
> https://github.com/apache/kafka/compare/trunk...SupermanScott:offset-reset-to-warn?diff=split&name=offset-reset-to-warn
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
