[ 
https://issues.apache.org/jira/browse/KAFKA-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999884#comment-14999884
 ] 

Mayuresh Gharat commented on KAFKA-2805:
----------------------------------------

I did this experiment :

1) I created a topic called "kip-19-followup" on one of our test cluster with 1 
partition and replication factor 1.

2) started the producer class :
./kafka-verifiable-producer.sh --topic kip-19-followup --broker-list (BROKER 
LIST) --max-messages 92233736 --acks 1

3) The producer started producing  and I could see : 
{"partition":0,"offset":3164368,"time_ms":1447212192651,"name":"producer_send_success","topic":"kip-19-followup","class":"class
 org.apache.kafka.tools.VerifiableProducer","value":"9547","key":null}

4) Then I killed the broker that was hosting this topic and I could see :
{"exception":"class 
org.apache.kafka.common.errors.TimeoutException","time_ms":1447212028704,"name":"producer_send_error","topic":"kip-19-followup","message":"Batch
 Expired","class":"class 
org.apache.kafka.tools.VerifiableProducer","value":"107100","key":null}

The producer did not hang. My broker is not on trunk though.

Thanks,

Mayuresh


> RecordAccumulator request timeout only enforced if partition leader is unknown
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-2805
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2805
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Mayuresh Gharat
>
> When no brokers are left in the cluster, the producer seems not to enforce 
> the request timeout as expected.
> From the user mailing list, the null check in batch expiration in 
> RecordAccumulator seems questionable: 
> https://github.com/apache/kafka/blob/ae5a5d7c08bb634576a414f6f2864c5b8a7e58a3/clients/src/main/java/org/apache/kafka/clients/producer/internals/RecordAccumulator.java#L220.
>  
> If this is correct behavior, it is probably worthwhile clarifying the purpose 
> of the check in a comment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to