You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/11/14 18:27:11 UTC

[jira] [Commented] (KAFKA-2624) Truncate warn message logged after truncating partitions

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

ASF GitHub Bot commented on KAFKA-2624:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/287


> Truncate warn message logged after truncating partitions
> --------------------------------------------------------
>
>                 Key: KAFKA-2624
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2624
>             Project: Kafka
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 0.6, 0.7, 0.7.1, 0.7.2, 0.8.0, 0.8.1, 0.8.1.1, 0.8.1.2, 0.8.2.0, 0.8.2.1, 0.9.0.0, 0.10.0.0, 0.8.2.2, 0.9.0.1
>            Reporter: Francois Visconte
>            Assignee: Neha Narkhede
>            Priority: Trivial
>             Fix For: 0.9.0.0
>
>
> Message warning about truncating is logged after log has been truncated. Consequently, logged message is always of the form
> Replica 13 for partition [topic_x,24] reset its fetch offset from 1234 to current leader 22's latest offset 1234 (kafka.server.ReplicaFetcherThread)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)