GitHub user vahidhashemian opened a pull request:
https://github.com/apache/kafka/pull/4241
KAFKA-4893: Fix conflict between async topic deletion and max topic length
With async topic deletion the topic partition folder name is affixed with a
'.', a UUID, and '-delete'. If topic name length is close to its current limit
(249) this could cause an issue because the folder name size goes over 255.
This PR implements the [suggestion
solution](https://issues.apache.org/jira/browse/KAFKA-4893?focusedCommentId=15927155)
by @onurkaraman in the JIRA.
This implementation is automatically backward compatible, and cleans up any
folder marked for deletion using the old method (affixing the folder name).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vahidhashemian/kafka KAFKA-4893
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/4241.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4241
----
commit b6f7f2cad7f8484aa35f22988ab7e4685607966f
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date: 2017-11-21T00:28:44Z
KAFKA-4893: Fix conflict between async topic deletion and max topic lenth
With async topic deletion the topic partition folder name is affixed with a
'.', a UUID, and '-delete'. If topic name length is close to its current limit
(249) this could cause an issue because the folder name size goes over 255.
This PR implements the [suggestion
solution](https://issues.apache.org/jira/browse/KAFKA-4893?focusedCommentId=15927155)
by @onurkaraman in the JIRA.
This implementation is automatically backward compatible, and cleans up any
folder marked for deletion using the old method (affixing the folder name).
----
---
