[
https://issues.apache.org/jira/browse/KAFKA-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533566#comment-15533566
]
ASF GitHub Bot commented on KAFKA-4232:
---------------------------------------
GitHub user becketqin opened a pull request:
https://github.com/apache/kafka/pull/1935
KAFKA-4232: make MemoryRecords.writable volatile.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/becketqin/kafka KAFKA-4232
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1935.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1935
----
commit 5b19237a34ab35c5d0dbaf473e6648249bb2fd6a
Author: Jiangjie Qin <[email protected]>
Date: 2016-09-29T17:55:24Z
KAFKA-4232
----
> IllegalStateException may be thrown from producer.send() when a batch is full.
> ------------------------------------------------------------------------------
>
> Key: KAFKA-4232
> URL: https://issues.apache.org/jira/browse/KAFKA-4232
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Priority: Blocker
> Fix For: 0.10.1.0
>
>
> We used to leave the batch not closed if an append failed due to batch is
> full. In KAFKA-3747, we changed the behavior to close the batch to save the
> memory. However, this would leave a closed batch at the end of the deque and
> may cause a subsequent append fail due to MemoryRecords not writable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
