[ https://issues.apache.org/jira/browse/KAFKA-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016065#comment-14016065 ]
Manasi Manasi commented on KAFKA-1479: -------------------------------------- Thanks for the reply, Jun. I will upgrade to 0.8.1.1. But why would this manifest all of a sudden? Most of the topics have been deleted a while back and I didn't see any logging issues. Also, if I switch to 0.8.1.1, is the check for deleted topics disabled? So that I won't see the log lines anymore. > Logs filling up while Kafka ReplicaFetcherThread tries to retrieve partition > info for deleted topics > ---------------------------------------------------------------------------------------------------- > > Key: KAFKA-1479 > URL: https://issues.apache.org/jira/browse/KAFKA-1479 > Project: Kafka > Issue Type: Bug > Components: log > Affects Versions: 0.8.1 > Environment: CentOS > Reporter: Manasi Manasi > Assignee: Jay Kreps > > Started noticing that logs are filling up fast with lines like this: > {quote} > [2014-06-01 15:18:08,218] WARN [KafkaApi-2] Fetch request with correlation id > 10049 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-27,26] > failed due to Topic sams_2014-05-27 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > [2014-06-01 15:18:08,218] WARN [KafkaApi-2] Fetch request with correlation id > 10049 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-28,38] > failed due to Topic sams_2014-05-28 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > [2014-06-01 15:18:08,219] WARN [KafkaApi-2] Fetch request with correlation id > 10049 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-30,20] > failed due to Topic sams_2014-05-30 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > [2014-06-01 15:18:08,219] WARN [KafkaApi-2] Fetch request with correlation id > 10049 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-22,46] > failed due to Topic sams_2014-05-22 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > [2014-06-01 15:18:08,219] WARN [KafkaApi-2] Fetch request with correlation id > 10049 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-27,8] > failed due to Topic sams_2014-05-27 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > {quote} > The above is from kafkaServer.out. Also seeing errors in server.log: > {quote} > [2014-06-01 15:23:52,788] ERROR [ReplicaFetcherThread-0-0], Error for > partition [sams_2014-05-26,19] to broker 0:class > kafka.common.UnknownTopicOrPartitionException > (kafka.server.ReplicaFetcherThread) > [2014-06-01 15:23:52,788] WARN [KafkaApi-2] Fetch request with correlation id > 10887 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-30,4] > failed due to Topic sams_2014-05-30 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > [2014-06-01 15:23:52,788] ERROR [ReplicaFetcherThread-0-0], Error for > partition [sams_2014-05-24,34] to broker 0:class > kafka.common.UnknownTopicOrPartitionException > (kafka.server.ReplicaFetcherThread) > [2014-06-01 15:23:52,788] ERROR [ReplicaFetcherThread-0-0], Error for > partition [sams_2014-05-26,41] to broker 0:class > kafka.common.UnknownTopicOrPartitionException > (kafka.server.ReplicaFetcherThread) > [2014-06-01 15:23:52,788] WARN [KafkaApi-2] Fetch request with correlation id > 10887 from client ReplicaFetcherThread-0-2 on partition [2014-05-21,0] failed > due to Topic 2014-05-21 either doesn't exist or is in the process of being > deleted (kafka.server.KafkaApis) > [2014-06-01 15:23:52,788] ERROR [ReplicaFetcherThread-0-0], Error for > partition [sams_2014-05-28,42] to broker 0:class > kafka.common.UnknownTopicOrPartitionException > (kafka.server.ReplicaFetcherThread) > [2014-06-01 15:23:52,788] ERROR [ReplicaFetcherThread-0-0], Error for > partition [sams_2014-05-22,21] to broker 0:class > kafka.common.UnknownTopicOrPartitionException > (kafka.server.ReplicaFetcherThread) > [2014-06-01 15:23:52,788] WARN [KafkaApi-2] Fetch request with correlation id > 10887 from client ReplicaFetcherThread-0-2 on partition [sams_2014-05-20,26] > failed due to Topic sams_2014-05-20 either doesn't exist or is in the process > of being deleted (kafka.server.KafkaApis) > {quote} > All these partitions belong to deleted topics. Nothing changed on our end > when we started noticing these logs filling up. Any ideas what is going on? -- This message was sent by Atlassian JIRA (v6.2#6252)