[
https://issues.apache.org/jira/browse/KAFKA-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742312#comment-16742312
]
Joseph Niemiec commented on KAFKA-7807:
---------------------------------------
Saddly I am unsure how the dev team created this, I only saw it while
performing on the operations side when it started creating the believed above
issue.
> Special Characters in Topic Name Appear to Break Replication
> ------------------------------------------------------------
>
> Key: KAFKA-7807
> URL: https://issues.apache.org/jira/browse/KAFKA-7807
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Joseph Niemiec
> Priority: Minor
>
> We recently upgraded a cluster from 1.0.0 to 1.1.1 and experienced an odd
> issue when we restarted the first broker. All ISR values quickly jumped to
> zero but no replication would take place to the broker, waiting over 30
> minutes nothing occurred. After some investigation we believe it was due to a
> un-used topic having been created with special characters. Once we deleted
> this topic and restarted the broker everything was fine. We did not replicate
> this issue to conform it is why replication resumed but the timing as near
> perfect for when the problem topic was deleted and replication resumed.
>
> Topic name (the quotes are part of the name)
> ```
> ‘service_prod_premium_out’
> ```
> Error Message we saw that lead us to decide to delete this topic.
> ```
> [2019-01-09 11:14:38,852] ERROR [KafkaApi-3] Error when handling request
> //Removed Partition and Replica Data
> {color:#FF0000}java.nio.file.InvalidPathException: Malformed input or input
> contains unmappable characters:
> /grid/7/kafka-logs/?service_prod_premium_out?-4{color}
> at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
> at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
> at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
> at java.io.File.toPath(File.java:2234)
> at kafka.log.LogManager.$anonfun$getOrCreateLog$1(LogManager.scala:676)
> at scala.Option.getOrElse(Option.scala:121)
> at kafka.log.LogManager.getOrCreateLog(LogManager.scala:646)
> at kafka.cluster.Partition.$anonfun$getOrCreateReplica$1(Partition.scala:178)
> at kafka.utils.Pool.getAndMaybePut(Pool.scala:65)
> at kafka.cluster.Partition.getOrCreateReplica(Partition.scala:174)
> at kafka.cluster.Partition.$anonfun$makeFollower$3(Partition.scala:316)
> at
> kafka.cluster.Partition.$anonfun$makeFollower$3$adapted(Partition.scala:316)
> at scala.collection.mutable.ResizableArray.foreach(ResizableArray.scala:59)
> at scala.collection.mutable.ResizableArray.foreach$(ResizableArray.scala:52)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
> at kafka.cluster.Partition.$anonfun$makeFollower$1(Partition.scala:316)
> at scala.runtime.java8.JFunction0$mcZ$sp.apply(JFunction0$mcZ$sp.java:12)
> at kafka.utils.CoreUtils$.inLock(CoreUtils.scala:250)
> at kafka.utils.CoreUtils$.inWriteLock(CoreUtils.scala:258)
> at kafka.cluster.Partition.makeFollower(Partition.scala:309)
> at
> kafka.server.ReplicaManager.$anonfun$makeFollowers$4(ReplicaManager.scala:1242)
> at scala.collection.mutable.HashMap.$anonfun$foreach$1(HashMap.scala:138)
> at scala.collection.mutable.HashTable.foreachEntry(HashTable.scala:236)
> at scala.collection.mutable.HashTable.foreachEntry$(HashTable.scala:229)
> at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:40)
> at scala.collection.mutable.HashMap.foreach(HashMap.scala:138)
> at kafka.server.ReplicaManager.makeFollowers(ReplicaManager.scala:1236)
> at
> kafka.server.ReplicaManager.becomeLeaderOrFollower(ReplicaManager.scala:1082)
> at kafka.server.KafkaApis.handleLeaderAndIsrRequest(KafkaApis.scala:183)
> at kafka.server.KafkaApis.handle(KafkaApis.scala:108)
> at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:69)
> at java.lang.Thread.run(Thread.java:748)
> ```
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
