[jira] [Commented] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

2016-12-09 Thread Rajini Sivaram (JIRA)
ttps://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer > Async producer send not retrying on TimeoutException: Batch Expired > --- > > Key: KAFKA-4515 >

[jira] [Commented] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

2016-12-09 Thread huxi (JIRA)
onse with correlation id {} on topic-partition {}, retrying ({} attempts left). Error" items in the producer log when enabling retry? > Async producer send not retrying on TimeoutException: Batch Expired > --- > >

[jira] [Updated] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

2016-12-08 Thread Di Shang (JIRA)
rue) { ProducerRecord record = new ProducerRecord<>("my-topic", i.toString()); send(record); Thread.sleep(100); i++; } } {code} What we found is that when we set *request.timeout.ms* to a small value like

[jira] [Created] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

2016-12-08 Thread Di Shang (JIRA)
Di Shang created KAFKA-4515: --- Summary: Async producer send not retrying on TimeoutException: Batch Expired Key: KAFKA-4515 URL: https://issues.apache.org/jira/browse/KAFKA-4515 Project: Kafka

[jira] [Commented] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-11-16 Thread ASF GitHub Bot (JIRA)
pull request at: https://github.com/apache/kafka/pull/1791 > KafkaProducer raises Batch Expired exception > - > > Key: KAFKA-4089 > URL: https://issues.apache.org/jira/browse/KAFKA-4089 >

Re: Batch Expired

2016-08-29 Thread Mayuresh Gharat
_gh...@comcast.com> wrote: > Hi Krishna, > Thank you for your response. > > Connections already made but if we increase the request timeout 5 times > let's say request.timeout.ms= 5*60000 , then the number of 'Batch > Expired ' exception is les

RE: Batch Expired

2016-08-29 Thread Ghosh, Achintya (Contractor)
Hi Krishna, Thank you for your response. Connections already made but if we increase the request timeout 5 times let's say request.timeout.ms= 5*6 , then the number of 'Batch Expired ' exception is less, so what is the recommended value for ' request.timeout.ms '

Re: Batch Expired

2016-08-26 Thread R Krishna
gt; What is the recommended Producer setting for Producer as I see a lot of > Batch Expired exception even though I put request.timeout=6. > > Producer settings: > acks=1 > retries=3 > batch.size=16384 > linger.ms=5 > buffer.memory=33554432 > request.timeout.ms=6000

[jira] [Assigned] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-26 Thread Sumant Tambe (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe reassigned KAFKA-4089: --- Assignee: Sumant Tambe (was: Dong Lin) > KafkaProducer raises Batch Expired except

Batch Expired

2016-08-26 Thread Ghosh, Achintya (Contractor)
Hi there, What is the recommended Producer setting for Producer as I see a lot of Batch Expired exception even though I put request.timeout=6. Producer settings: acks=1 retries=3 batch.size=16384 linger.ms=5 buffer.memory=33554432 request.timeout.ms=6 timeout.ms=6 Thanks Achintya

[jira] [Commented] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread ASF GitHub Bot (JIRA)
uest: https://github.com/apache/kafka/pull/1791 KAFKA-4089: KafkaProducer expires batch when metadata is stale You can merge this pull request into a Git repository by running: $ git pull https://github.com/sutambe/kafka batch-expired Alternatively you can review and apply t

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Sumant Tambe (JIRA)
xpire batches only when the following is true # meta-data is fresh AND # batch remained in the queue longer than request timeout. > KafkaProducer raises Batch Expired exception > - > > Key: KAFKA-4089 > URL:

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Sumant Tambe (JIRA)
but not sufficient. It should additionally restrict ejection when metadata is stale. Conversely, it should expire batches only when the following is true # !muted AND # meta-data is fresh but leader not available # batch remained in the queue longer than request timeout. &

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Sumant Tambe (JIRA)
the following is true # !muted AND # meta-data is fresh but leader not available # batch remained in the queue longer than request timeout. > KafkaProducer raises Batch Expired exception > - > > Key: KAFKA-4089 >

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Sumant Tambe (JIRA)
ches only when the following is true # !muted AND # meta-data is fresh but leader not available > KafkaProducer raises Batch Expired exception > - > > Key: KAFKA-4089 > URL: https://issues.apache.org/

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Sumant Tambe (JIRA)
meta-data is fresh but leader not available > KafkaProducer raises Batch Expired exception > - > > Key: KAFKA-4089 > URL: https://issues.apache.org/jira/browse/KAFKA-4089 > Project: Kafka

[jira] [Assigned] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Dong Lin (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-4089: --- Assignee: Dong Lin > KafkaProducer raises Batch Expired except

[jira] [Created] (KAFKA-4089) KafkaProducer raises Batch Expired exception

2016-08-25 Thread Sumant Tambe (JIRA)
Sumant Tambe created KAFKA-4089: --- Summary: KafkaProducer raises Batch Expired exception Key: KAFKA-4089 URL: https://issues.apache.org/jira/browse/KAFKA-4089 Project: Kafka Issue Type: Bug