[
https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035862#comment-16035862
]
huxihx commented on KAFKA-5296:
-------------------------------
[~asaikia] Do you mean directories for some partitions could always fail to be
created after issuing create-topic command? That seems to be a separate issue
although I am unsure if it relates to your original one. Could you check broker
log for any other exceptions showing why file directories got failed to create?
> Unable to write to some partitions of newly created topic in 10.2
> -----------------------------------------------------------------
>
> Key: KAFKA-5296
> URL: https://issues.apache.org/jira/browse/KAFKA-5296
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.2.0
> Reporter: Abhisek Saikia
>
> We are using kafka 10.2 and the cluster was running fine for a month with 50
> topics and now we are having issue in producing message by creating new
> topics. The create topic command is successful but producers are throwing
> error while writing to some partitions.
> Error in producer-
> java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for
> [topic1]-8: 30039 ms has passed since batch creation plus linger time
> at
> org.apache.kafka.clients.producer.internals.FutureRecordMetadata.valueOrError(FutureRecordMetadata.java:70)
> ~[kafka-clients-0.10.2.0.jar:na]
> at
> org.apache.kafka.clients.producer.internals.FutureRecordMetadata.get(FutureRecordMetadata.java:57)
> ~[kafka-clients-0.10.2.0.jar:na]
> at
> org.apache.kafka.clients.producer.internals.FutureRecordMetadata.get(FutureRecordMetadata.java:25)
> ~[kafka-clients-0.10.2.0.jar:na]
> On the broker side, I don't see any topic-parition folder getting created for
> the broker who is the leader for the partition.
> While using 0.8 client, the write used to hang while it starts writing to the
> partition having this issue. With 10.2 it resolved the the producer hang issue
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)