You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Yu Yang (JIRA)" <ji...@apache.org> on 2015/06/03 08:53:49 UTC
[jira] [Commented] (KAFKA-2243) Topic partition replica got reset
due to ReplicaFetcherThread request out of range
[ https://issues.apache.org/jira/browse/KAFKA-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570381#comment-14570381 ]
Yu Yang commented on KAFKA-2243:
--------------------------------
It seems that this issue has been reported in https://issues.apache.org/jira/browse/KAFKA-2165. Resolving this as duplicate.
> Topic partition replica got reset due to ReplicaFetcherThread request out of range
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-2243
> URL: https://issues.apache.org/jira/browse/KAFKA-2243
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1
> Environment: Ubuntu 12.04.5 LTS, java version "1.7.0_67", command line:
> /usr/bin/java -Xms3g -Xmx3g -XX:NewSize=256m -XX:MaxNewSize=256m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=70 -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintTenuringDistribution -Xloggc:/var/log/kafka/gc.log -Djava.awt.headless=true -Dlog4j.configuration=file:/etc/kafka/log4j.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=9999 -cp :/usr/local/libs/jopt-simple-3.2.jar:/usr/local/libs/kafka-clients-0.8.2.1.jar:/usr/local/libs/kafka_2.10-0.8.2.1-javadoc.jar:/usr/local/libs/kafka_2.10-0.8.2.1-scaladoc.jar:/usr/local/libs/kafka_2.10-0.8.2.1-sources.jar:/usr/local/libs/kafka_2.10-0.8.2.1-test.jar:/usr/local/libs/kafka_2.10-0.8.2.1.jar:/usr/local/libs/log4j-1.2.16.jar:/usr/local/libs/lz4-1.2.0.jar:/usr/local/libs/metrics-core-2.2.0.jar:/usr/local/libs/scala-library-2.10.4.jar:/usr/local/libs/slf4j-api-1.7.6.jar:/usr/local/libs/slf4j-log4j12-1.6.1.jar:/usr/local/libs/snappy-java-1.1.1.6.jar:/usr/local/libs/zkclient-0.3.jar:/usr/local/libs/zookeeper-3.4.6.jar kafka.Kafka /etc/kafka/server.properties
> Reporter: Yu Yang
> Priority: Critical
>
> We are running a kafka 0.8.2.1 cluster. We found that topic partition replica often got reset for replication. The following is what we usually found in the log.
> It seems that this is related to https://issues.apache.org/jira/browse/KAFKA-1806. But KAFKA-1806 has been resolved. Is this a new issue in kafka 0.8.2.1?
> [2015-06-03 05:46:40,760] ERROR [ReplicaFetcherThread-1-4069], Current offset 308834471 for partition [request_log,192] out of range; reset offset to 198327005 (kafka.server.ReplicaFetcherThread)
> The following is the command line that we use for kafka:
> /usr/bin/java -Xms3g -Xmx3g -XX:NewSize=256m -XX:MaxNewSize=256m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=70 -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintTenuringDistribution -Xloggc:/var/log/kafka/gc.log -Djava.awt.headless=true -Dlog4j.configuration=file:/etc/kafka/log4j.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=9999 -cp :/usr/local/libs/jopt-simple-3.2.jar:/usr/local/libs/kafka-clients-0.8.2.1.jar:/usr/local/libs/kafka_2.10-0.8.2.1-javadoc.jar:/usr/local/libs/kafka_2.10-0.8.2.1-scaladoc.jar:/usr/local/libs/kafka_2.10-0.8.2.1-sources.jar:/usr/local/libs/kafka_2.10-0.8.2.1-test.jar:/usr/local/libs/kafka_2.10-0.8.2.1.jar:/usr/local/libs/log4j-1.2.16.jar:/usr/local/libs/lz4-1.2.0.jar:/usr/local/libs/metrics-core-2.2.0.jar:/usr/local/libs/scala-library-2.10.4.jar:/usr/local/libs/slf4j-api-1.7.6.jar:/usr/local/libs/slf4j-log4j12-1.6.1.jar:/usr/local/libs/snappy-java-1.1.1.6.jar:/usr/local/libs/zkclient-0.3.jar:/usr/local/libs/zookeeper-3.4.6.jar kafka.Kafka /etc/kafka/server.properties
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)