[
https://issues.apache.org/jira/browse/KAFKA-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212016#comment-16212016
]
Jun Rao commented on KAFKA-6093:
--------------------------------
This seem to happen only in the 1.0 branch. The issue seems to be that in
LogManager.asyncDelete(), we call removedLog.close() and then enqueue the log
for deletion. Then in Log.delete(), we first call checkIfLogOffline() and will
hit KafkaStorageException since the log is marked as closed by
removedLog.close().
[~lindong], do you think you could take a look at this?
> replica dir not deleted after topic deletion
> --------------------------------------------
>
> Key: KAFKA-6093
> URL: https://issues.apache.org/jira/browse/KAFKA-6093
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.0
> Reporter: Jun Rao
> Priority: Blocker
>
> Did the following test.
> 1. bin/kafka-topics.sh --zookeeper localhost:2181 --topic test --partitions
> 1 --replication-factor 1 --create
> 2. bin/kafka-topics.sh --zookeeper localhost:2181 --topic test --delete
> Saw the following in the broker log.
> {code:java}
> [2017-10-19 17:54:43,413] INFO Log for partition test-0 is renamed to
> /tmp/kafka-logs/test-0.0b578c684ec540b48bf63ecec1752f02-delete and is
> scheduled for deletion (kafka.log.LogManager)
> [2017-10-19 17:55:27,034] ERROR Exception while deleting
> Log(/tmp/kafka-logs/test-0.0b578c684ec540b48bf63ecec1752f02-delete) in dir
> /tmp/kafka-logs. (kafka.log.LogManager)
> org.apache.kafka.common.errors.KafkaStorageException: The log for partition
> test-0 is offline
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
