Any followup on if there is some problems in deleting topics in new version
of Kafka (kafka_2.10-0.10.2.0-SNAPSHOT).

I have also noticed some testcases failed around these lines:

org.apache.kafka.streams.integration.JoinIntegrationTest >
testInnerKStreamKTable FAILED
    org.apache.kafka.common.errors.TopicExistsException: Topic
"inputTopicLeft" already exists.

    kafka.common.TopicAlreadyMarkedForDeletionException: topic
inputTopicLeft is already marked for deletion
        at kafka.admin.AdminUtils$.deleteTopic(AdminUtils.scala:323)
        at kafka.admin.AdminUtils.deleteTopic(AdminUtils.scala)
        at
org.apache.kafka.streams.integration.utils.KafkaEmbedded.deleteTopic(KafkaEmbedded.java:200)
        at
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.deleteTopic(EmbeddedKafkaCluster.java:157)
        at
org.apache.kafka.streams.integration.JoinIntegrationTest.cleanup(JoinIntegrationTest.java:159)

What happens is the topic is marked for deletion but never deleted and
underlying issue is it fails to rename log directory -delete

Not sure if all these issues are related.

Thanks
Sachin


On Thu, Dec 15, 2016 at 12:03 PM, Sachin Mittal <sjmit...@gmail.com> wrote:

> Also to let you all know I get this error too on server console
> log4j:ERROR Failed to rename 
> [D:\kafka_2.10-0.10.2.0-SNAPSHOT/logs/controller.log]
> to [D:\kafka_2.10-0.10.2.0-SNAPSHOT/logs/controller.log.2016-12-15-11].
>
> Looks like related. It seems some central process in new version if
> failing to rename files.
>
> Thanks
> Sachin
>
>
> On Wed, Dec 14, 2016 at 10:29 PM, Sachin Mittal <sjmit...@gmail.com>
> wrote:
>
>> I created a new topic from shell.
>> I published some messages to it via java producer thread and consume some
>> messages via streams application.
>> Then I terminated streams application using ctrl c.
>>
>> Then I delete the topic via shell.
>>
>> I get this exception.
>>
>> [2016-12-14 22:24:43,529] ERROR [KafkaApi-0] Error when handling request
>> {controller_id=0,controller_epoch=1,delete_partitions=true,
>> partitions=[{topic=test-window-stream,partition=0}]}
>> (kafka.server.KafkaApis)
>> kafka.common.KafkaStorageException: Failed to rename log directory from
>> D:\tmp\kafka-logs\test-window-stream-0 to D:\tmp\kafka-logs\test-window-
>> stream-0.b21fedf3f87040c4aa76cd3f96e7bd31-delete
>>         at kafka.log.LogManager.asyncDelete(LogManager.scala:451)
>>         at kafka.cluster.Partition$$anonfun$delete$1.apply$mcV$sp(Parti
>> tion.scala:164)
>>         at kafka.cluster.Partition$$anonfun$delete$1.apply(Partition.
>> scala:158)
>>         at kafka.cluster.Partition$$anonfun$delete$1.apply(Partition.
>> scala:158)
>>
>> The same process used to delete the topic when using kafka_2.10-0.10.0.1.
>> I am right now using  kafka_2.10-0.10.2.0-SNAPSHOT.
>>
>> Note if I delete same topic before publishing any message then it deletes.
>> Looks like some process is keeping a lock on the perpetually.
>>
>> Thanks
>> Sachin
>>
>>
>> On Wed, Dec 14, 2016 at 12:44 AM, Apurva Mehta <apu...@confluent.io>
>> wrote:
>>
>>> How are you trying to delete the topic? Next time this occurs, can you
>>> check whether the process has permissions to perform that operation?
>>>
>>> On Mon, Dec 12, 2016 at 10:55 PM, Sachin Mittal <sjmit...@gmail.com>
>>> wrote:
>>>
>>> > Hi,
>>> > I recently built an application from source and I get the following
>>> > exception when trying to delete a topic
>>> >
>>> > kafka.common.KafkaStorageException: Failed to rename log directory
>>> from
>>> > D:\tmp\kafka-logs\test-window-stream-0 to
>>> > D:\tmp\kafka-logs\test-window-stream-0.0ce9f9150000431397d1c2dad4f535
>>> > a3-delete
>>> >         at kafka.log.LogManager.asyncDelete(LogManager.scala:451)
>>> >         at
>>> > kafka.cluster.Partition$$anonfun$delete$1.apply$mcV$sp(
>>> > Partition.scala:164)
>>> >
>>> >
>>> > Note that I have set delete.topic.enable=true
>>> >
>>> > Also this was all working fine when using kafka_2.10-0.10.0.1.
>>> > Issue happens with kafka_2.10-0.10.2.0-SNAPSHOT
>>> >
>>> > Thanks
>>> > Sachin
>>> >
>>>
>>
>>
>

Reply via email to