[
https://issues.apache.org/jira/browse/KAFKA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145586#comment-13145586
]
Pierre-Yves Ritschard commented on KAFKA-196:
---------------------------------------------
I tried coming up with a sensible and not limitative number which will
not clash with MAXPATHLEN when prefixing with the log directory. Some
old systems are rumored to have it as low as 256, but I don't see many
use cases where very large topic strings are relevant. It could safely
be bumped to 1000 (which would leave 23 chars for the prefix path).
Java has no way of accessing MAXPATHLEN unfortunately, since it is OS-specific
On Mon, Nov 7, 2011 at 5:12 PM, Jun Rao (Commented) (JIRA)
> Topic creation fails on large values
> ------------------------------------
>
> Key: KAFKA-196
> URL: https://issues.apache.org/jira/browse/KAFKA-196
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Pierre-Yves Ritschard
> Attachments:
> 0001-Set-a-hard-limit-on-topic-width-this-fixes-KAFKA-196.patch
>
>
> Since topic logs are stored in a directory holding the topic's name, creation
> of the directory might fail for large strings.
> This is not a problem per-se but the exception thrown is rather cryptic and
> hard to figure out for operations.
> I propose fixing this temporarily with a hard limit of 200 chars for topic
> names, it would also be possible to hash the topic name.
> Another concern is that the exception raised stops the broker, effectively
> creating a simple DoS vector, I'm concerned about how tests or wrong client
> library usage can take down the whole broker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
