[jira] [Commented] (KAFKA-6961) UnknownTopicOrPartitionException & NotLeaderForPartitionException upon replication of topics.
[ https://issues.apache.org/jira/browse/KAFKA-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586615#comment-16586615 ] Jiangtao Liu commented on KAFKA-6961: - I encounter the same issue after I move Kafka server to new EC2 server. so any idea to solve it? or simply ignore it since our replica is functional well. > UnknownTopicOrPartitionException & NotLeaderForPartitionException upon > replication of topics. > - > > Key: KAFKA-6961 > URL: https://issues.apache.org/jira/browse/KAFKA-6961 > Project: Kafka > Issue Type: Bug > Environment: kubernetes cluster kafka. >Reporter: kaushik srinivas >Assignee: praveen >Priority: Major > Attachments: k8s_NotLeaderForPartition.txt, k8s_replication_errors.txt > > > Running kafka & zookeeper in kubernetes cluster. > No of brokers : 3 > No of partitions per topic : 3 > creating topic with 3 partitions, and looks like all the partitions are up. > Below is the snapshot to confirm the same, > Topic:applestore PartitionCount:3 ReplicationFactor:3 Configs: > Topic: applestore Partition: 0Leader: 1001Replicas: > 1001,1003,1002Isr: 1001,1003,1002 > Topic: applestore Partition: 1Leader: 1002Replicas: > 1002,1001,1003Isr: 1002,1001,1003 > Topic: applestore Partition: 2Leader: 1003Replicas: > 1003,1002,1001Isr: 1003,1002,1001 > > But, we see in the brokers as soon as the topics are created below stack > traces appears, > > error 1: > [2018-05-28 08:00:31,875] ERROR [ReplicaFetcher replicaId=1001, > leaderId=1003, fetcherId=7] Error for partition applestore-2 to broker > 1003:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This > server does not host this topic-partition. (kafka.server.ReplicaFetcherThread) > > error 2 : > [2018-05-28 00:43:20,993] ERROR [ReplicaFetcher replicaId=1003, > leaderId=1001, fetcherId=0] Error for partition apple-6 to broker > 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This > server is not the leader for that topic-partition. > (kafka.server.ReplicaFetcherThread) > > When we tries producing records to each specific partition, it works fine and > also log size across the replicated brokers appears to be equal, which means > replication is happening fine. > Attaching the two stack trace files. > > Why are these stack traces appearing ? can we ignore these stack traces if > its some spam messages ? > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KAFKA-6961) UnknownTopicOrPartitionException & NotLeaderForPartitionException upon replication of topics.
[
https://issues.apache.org/jira/browse/KAFKA-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493640#comment-16493640
]
praveen commented on KAFKA-6961:
I am seeing similar log entry in non-leader broker's when creating topics. This
can be ignored as long as all the replicas are in-sync.
public class UnknownTopicOrPartitionException extends
[InvalidMetadataException|https://kafka.apache.org/11/javadoc/org/apache/kafka/common/errors/InvalidMetadataException.html]
This topic/partition doesn't exist. This exception is used in contexts where a
topic doesn't seem to exist based on possibly stale metadata.
{color:#14892c}*{color:#33}This exception is retriable because the topic or
partition might subsequently be created{color}.*{color}
> UnknownTopicOrPartitionException & NotLeaderForPartitionException upon
> replication of topics.
> -
>
> Key: KAFKA-6961
> URL: https://issues.apache.org/jira/browse/KAFKA-6961
> Project: Kafka
> Issue Type: Bug
> Environment: kubernetes cluster kafka.
>Reporter: kaushik srinivas
>Priority: Major
> Attachments: k8s_NotLeaderForPartition.txt, k8s_replication_errors.txt
>
>
> Running kafka & zookeeper in kubernetes cluster.
> No of brokers : 3
> No of partitions per topic : 3
> creating topic with 3 partitions, and looks like all the partitions are up.
> Below is the snapshot to confirm the same,
> Topic:applestore PartitionCount:3 ReplicationFactor:3 Configs:
> Topic: applestore Partition: 0Leader: 1001Replicas:
> 1001,1003,1002Isr: 1001,1003,1002
> Topic: applestore Partition: 1Leader: 1002Replicas:
> 1002,1001,1003Isr: 1002,1001,1003
> Topic: applestore Partition: 2Leader: 1003Replicas:
> 1003,1002,1001Isr: 1003,1002,1001
>
> But, we see in the brokers as soon as the topics are created below stack
> traces appears,
>
> error 1:
> [2018-05-28 08:00:31,875] ERROR [ReplicaFetcher replicaId=1001,
> leaderId=1003, fetcherId=7] Error for partition applestore-2 to broker
> 1003:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This
> server does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
>
> error 2 :
> [2018-05-28 00:43:20,993] ERROR [ReplicaFetcher replicaId=1003,
> leaderId=1001, fetcherId=0] Error for partition apple-6 to broker
> 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This
> server is not the leader for that topic-partition.
> (kafka.server.ReplicaFetcherThread)
>
> When we tries producing records to each specific partition, it works fine and
> also log size across the replicated brokers appears to be equal, which means
> replication is happening fine.
> Attaching the two stack trace files.
>
> Why are these stack traces appearing ? can we ignore these stack traces if
> its some spam messages ?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KAFKA-6961) UnknownTopicOrPartitionException & NotLeaderForPartitionException upon replication of topics.
[ https://issues.apache.org/jira/browse/KAFKA-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493167#comment-16493167 ] Manikumar commented on KAFKA-6961: -- Are you observing these error logs continuously? If they are only seen during topic creation, then you can ignore these transient errors. If they are frequent, you can investigate for any frequent leader change, ISR shrink/expand etc.. > UnknownTopicOrPartitionException & NotLeaderForPartitionException upon > replication of topics. > - > > Key: KAFKA-6961 > URL: https://issues.apache.org/jira/browse/KAFKA-6961 > Project: Kafka > Issue Type: Bug > Environment: kubernetes cluster kafka. >Reporter: kaushik srinivas >Priority: Major > Attachments: k8s_NotLeaderForPartition.txt, k8s_replication_errors.txt > > > Running kafka & zookeeper in kubernetes cluster. > No of brokers : 3 > No of partitions per topic : 3 > creating topic with 3 partitions, and looks like all the partitions are up. > Below is the snapshot to confirm the same, > Topic:applestore PartitionCount:3 ReplicationFactor:3 Configs: > Topic: applestore Partition: 0Leader: 1001Replicas: > 1001,1003,1002Isr: 1001,1003,1002 > Topic: applestore Partition: 1Leader: 1002Replicas: > 1002,1001,1003Isr: 1002,1001,1003 > Topic: applestore Partition: 2Leader: 1003Replicas: > 1003,1002,1001Isr: 1003,1002,1001 > > But, we see in the brokers as soon as the topics are created below stack > traces appears, > > error 1: > [2018-05-28 08:00:31,875] ERROR [ReplicaFetcher replicaId=1001, > leaderId=1003, fetcherId=7] Error for partition applestore-2 to broker > 1003:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This > server does not host this topic-partition. (kafka.server.ReplicaFetcherThread) > > error 2 : > [2018-05-28 00:43:20,993] ERROR [ReplicaFetcher replicaId=1003, > leaderId=1001, fetcherId=0] Error for partition apple-6 to broker > 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This > server is not the leader for that topic-partition. > (kafka.server.ReplicaFetcherThread) > > When we tries producing records to each specific partition, it works fine and > also log size across the replicated brokers appears to be equal, which means > replication is happening fine. > Attaching the two stack trace files. > > Why are these stack traces appearing ? can we ignore these stack traces if > its some spam messages ? > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
