Re: [Java New Producer Kafka Trunk ] Need a State Check API Method

I agree with that statement that if producer is closed and try to send message it will give close. What we have done is wrap the NEW Producer API with Old Producer API. So when I use same code with OLD I do not get this issue. It is only problem with NEW Producer. Regardless of close, state I t

[jira] [Comment Edited] (KAFKA-1621) Standardize --messages option in perf scripts

[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161443#comment-14161443 ] Manikumar Reddy edited comment on KAFKA-1621 at 10/7/14 4:13 AM: ---

[jira] [Commented] (KAFKA-1621) Standardize --messages option in perf scripts

[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161443#comment-14161443 ] Manikumar Reddy commented on KAFKA-1621: [~jkreps] would like to work on this issu

[jira] [Created] (KAFKA-1680) JmxTool exits if no arguments are given

Ryan Berdeen created KAFKA-1680: --- Summary: JmxTool exits if no arguments are given Key: KAFKA-1680 URL: https://issues.apache.org/jira/browse/KAFKA-1680 Project: Kafka Issue Type: Bug Affec

[jira] [Resolved] (KAFKA-1672) zk timeouts with examples from 8.1.1.1

[ https://issues.apache.org/jira/browse/KAFKA-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Sandoz resolved KAFKA-1672. --- Resolution: Not a Problem Reviewer: Matthew Sandoz > zk timeouts with examples from 8.1.

[jira] [Commented] (KAFKA-1672) zk timeouts with examples from 8.1.1.1

[ https://issues.apache.org/jira/browse/KAFKA-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161350#comment-14161350 ] Matthew Sandoz commented on KAFKA-1672: --- ok i reconfigured one of my routers. there

Jenkins build is back to normal : Kafka-trunk #290

See

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161318#comment-14161318 ] Gwen Shapira commented on KAFKA-1667: - Looks like LogConfig has very few validations.

[jira] [Created] (KAFKA-1679) JmxTool outputs nothing if any mbean attributes can't be retrieved

Ryan Berdeen created KAFKA-1679: --- Summary: JmxTool outputs nothing if any mbean attributes can't be retrieved Key: KAFKA-1679 URL: https://issues.apache.org/jira/browse/KAFKA-1679 Project: Kafka

Re: Review Request 26346: Patch for KAFKA-1670

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26346/#review55619 --- core/src/main/scala/kafka/log/Log.scala

[jira] [Resolved] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1430. Resolution: Fixed The reverted change is committed in a followup patch in KAFKA-1468. > Purgatory redesign

[jira] [Commented] (KAFKA-1468) Improve perf tests

[ https://issues.apache.org/jira/browse/KAFKA-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161267#comment-14161267 ] Jun Rao commented on KAFKA-1468: Thanks for the followup patch. +1. Committed to trunk and

[jira] [Updated] (KAFKA-1668) TopicCommand doesn't warn if --topic argument doesn't match any topics

[ https://issues.apache.org/jira/browse/KAFKA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1668: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed, thanks. > TopicCommand does

Re: Review Request 26373: Patch for KAFKA-1647

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26373/#review55615 --- Since now the first iteration of "if" statements is only used for lo

Re: Review Request 26346: Patch for KAFKA-1670

> On Oct. 6, 2014, 5:24 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/log/Log.scala, line 502 > > > > > > We probably should enforce that a segment is never larger than > > config.segmentSize. So, if messageSize

[jira] [Commented] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161218#comment-14161218 ] Guozhang Wang commented on KAFKA-1430: -- Gone through the change list from May 6th (fi

[jira] [Updated] (KAFKA-1468) Improve perf tests

[ https://issues.apache.org/jira/browse/KAFKA-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1468: - Attachment: KAFKA-1468.patch > Improve perf tests > -- > > Key: KA

Review Request 26393: Follow-up KAFKA-1468

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26393/ --- Review request for kafka. Bugs: KAFKA-1468 https://issues.apache.org/jira/b

[jira] [Commented] (KAFKA-1468) Improve perf tests

[ https://issues.apache.org/jira/browse/KAFKA-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161211#comment-14161211 ] Guozhang Wang commented on KAFKA-1468: -- Created reviewboard https://reviews.apache.or

[jira] [Commented] (KAFKA-1670) Corrupt log files for segment.bytes values close to Int.MaxInt

[ https://issues.apache.org/jira/browse/KAFKA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161207#comment-14161207 ] Gwen Shapira commented on KAFKA-1670: - Makes sense. Thanks [~jkreps] > Corrupt log fi

[jira] [Resolved] (KAFKA-1468) Improve perf tests

[ https://issues.apache.org/jira/browse/KAFKA-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1468. Resolution: Fixed Fix Version/s: 0.8.2 Assignee: Jay Kreps Resolving the jira since it's alr

[jira] [Updated] (KAFKA-1674) auto.create.topics.enable docs are misleading

[ https://issues.apache.org/jira/browse/KAFKA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1674: --- Labels: newbie (was: ) > auto.create.topics.enable docs are misleading >

[jira] [Commented] (KAFKA-1677) Governor on concurrent replica reassignments

[ https://issues.apache.org/jira/browse/KAFKA-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161188#comment-14161188 ] Jay Kreps commented on KAFKA-1677: -- Agreed, LinkedIn is doing a similar thing. This shoul

[jira] [Commented] (KAFKA-1644) Inherit FetchResponse from RequestOrResponse

[ https://issues.apache.org/jira/browse/KAFKA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161187#comment-14161187 ] Jun Rao commented on KAFKA-1644: Perhaps it's better to throw a UnsupportedOperationExcept

[jira] [Commented] (KAFKA-1670) Corrupt log files for segment.bytes values close to Int.MaxInt

[ https://issues.apache.org/jira/browse/KAFKA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161185#comment-14161185 ] Jay Kreps commented on KAFKA-1670: -- Actually the reason for limiting the segments to 4GB

[jira] [Commented] (KAFKA-1670) Corrupt log files for segment.bytes values close to Int.MaxInt

[ https://issues.apache.org/jira/browse/KAFKA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161167#comment-14161167 ] Gwen Shapira commented on KAFKA-1670: - I think we'll want to change the segment size v

[jira] [Commented] (KAFKA-1641) Log cleaner exits if last cleaned offset is lower than earliest offset

[ https://issues.apache.org/jira/browse/KAFKA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161121#comment-14161121 ] Guozhang Wang commented on KAFKA-1641: -- Created reviewboard https://reviews.apache.or

[jira] [Updated] (KAFKA-1641) Log cleaner exits if last cleaned offset is lower than earliest offset

[ https://issues.apache.org/jira/browse/KAFKA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1641: - Attachment: KAFKA-1641.patch > Log cleaner exits if last cleaned offset is lower than earliest off

[jira] [Updated] (KAFKA-1641) Log cleaner exits if last cleaned offset is lower than earliest offset

[ https://issues.apache.org/jira/browse/KAFKA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1641: - Assignee: Guozhang Wang Status: Patch Available (was: Open) > Log cleaner exits if last cle

Review Request 26390: Fix KAFKA-1641

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26390/ --- Review request for kafka. Bugs: KAFKA-1641 https://issues.apache.org/jira/b

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160927#comment-14160927 ] Magnus Edenhill commented on KAFKA-1367: May I suggest not to change the protocol

[jira] [Updated] (KAFKA-1555) provide strong consistency with reasonable availability

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1555: Attachment: KAFKA-1555.6.patch Latest version, based on RB discussion. > provide strong consistency

Re: Review Request 25886: KAFKA-1555: provide strong consistency with reasonable availability

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25886/ --- (Updated Oct. 6, 2014, 8:28 p.m.) Review request for kafka. Changes ---

[jira] [Commented] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160848#comment-14160848 ] Gwen Shapira commented on KAFKA-1678: - 1. It just seems like a reasonable thing to sup

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160828#comment-14160828 ] Jay Kreps commented on KAFKA-1305: -- Well I guess the point is that they shouldn't be mutu

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160815#comment-14160815 ] Andrew Olson commented on KAFKA-1305: - > from my perspective being able to enable auto

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160789#comment-14160789 ] Jay Kreps commented on KAFKA-1305: -- FWIW, from my perspective being able to enable auto l

[jira] [Updated] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1678: - Reviewer: Neha Narkhede > add new options for reassign partition to better manager dead brokers >

[jira] [Commented] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160783#comment-14160783 ] Neha Narkhede commented on KAFKA-1678: -- What is the purpose of replace replica? If th

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160772#comment-14160772 ] Neha Narkhede commented on KAFKA-1367: -- The ISR cache on the broker was added only be

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160717#comment-14160717 ] Guozhang Wang commented on KAFKA-1367: -- Just talked to Joel offline. I think since IS

[jira] [Assigned] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-1678: --- Assignee: Gwen Shapira > add new options for reassign partition to better manager dead broker

[jira] [Updated] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1678: - Labels: operations (was: ) > add new options for reassign partition to better manager dead brokers >

[jira] [Updated] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1678: - Description: this is in two forms --replace-replica which is from broker.id to broker.id and --remov

[jira] [Updated] (KAFKA-1678) add new options for reassign partition to better manager dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1678: - Summary: add new options for reassign partition to better manager dead brokers (was: add new options for

[jira] [Created] (KAFKA-1678) add new options for reassign partition to in service a replacement replica for another one

Joe Stein created KAFKA-1678: Summary: add new options for reassign partition to in service a replacement replica for another one Key: KAFKA-1678 URL: https://issues.apache.org/jira/browse/KAFKA-1678 Proj

[jira] [Created] (KAFKA-1677) Governor on concurrent replica reassignments

Ryan Berdeen created KAFKA-1677: --- Summary: Governor on concurrent replica reassignments Key: KAFKA-1677 URL: https://issues.apache.org/jira/browse/KAFKA-1677 Project: Kafka Issue Type: New Feat

Re: Review Request 26346: Patch for KAFKA-1670

> On Oct. 6, 2014, 5:24 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/log/Log.scala, line 502 > > > > > > We probably should enforce that a segment is never larger than > > config.segmentSize. So, if messageSize

[jira] [Created] (KAFKA-1676) Ability to cancel replica reassignment in progress

Ryan Berdeen created KAFKA-1676: --- Summary: Ability to cancel replica reassignment in progress Key: KAFKA-1676 URL: https://issues.apache.org/jira/browse/KAFKA-1676 Project: Kafka Issue Type: Ne

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160538#comment-14160538 ] Guozhang Wang commented on KAFKA-1367: -- Regarding the fix to this issue, we can eithe

Re: Review Request 26346: Patch for KAFKA-1670

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26346/#review55526 --- core/src/main/scala/kafka/log/Log.scala

Re: Review Request 25995: Patch for KAFKA-1650

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25995/ --- (Updated Oct. 6, 2014, 5:20 p.m.) Review request for kafka. Bugs: KAFKA-1650

[jira] [Updated] (KAFKA-1650) Mirror Maker could lose data on unclean shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1650: Attachment: KAFKA-1650_2014-10-06_10:17:46.patch > Mirror Maker could lose data on unclean shutdown.

[jira] [Commented] (KAFKA-1650) Mirror Maker could lose data on unclean shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160526#comment-14160526 ] Jiangjie Qin commented on KAFKA-1650: - Updated reviewboard https://reviews.apache.org/

Re: Review Request 25995: Patch for KAFKA-1650

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25995/ --- (Updated Oct. 6, 2014, 5:17 p.m.) Review request for kafka. Bugs: KAFKA-1650

Re: Review Request 26346: Patch for KAFKA-1670

> On Oct. 5, 2014, 11:35 p.m., Jun Rao wrote: > > core/src/test/scala/unit/kafka/log/LogTest.scala, lines 113-129 > > > > > > Appending 2GB of data in a unit test is probably too long. We can > > probably just manuall

[jira] [Commented] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160513#comment-14160513 ] Jay Kreps commented on KAFKA-1430: -- Yes it was committed. > Purgatory redesign > ---

[jira] [Commented] (KAFKA-1647) Replication offset checkpoints (high water marks) can be lost on hard kills and restarts

[ https://issues.apache.org/jira/browse/KAFKA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160510#comment-14160510 ] Jiangjie Qin commented on KAFKA-1647: - Created reviewboard https://reviews.apache.org/

Review Request 26373: Patch for KAFKA-1647

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26373/ --- Review request for kafka. Bugs: KAFKA-1647 https://issues.apache.org/jira/b

[jira] [Updated] (KAFKA-1647) Replication offset checkpoints (high water marks) can be lost on hard kills and restarts

[ https://issues.apache.org/jira/browse/KAFKA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1647: Attachment: KAFKA-1647.patch > Replication offset checkpoints (high water marks) can be lost on hard

[jira] [Updated] (KAFKA-1647) Replication offset checkpoints (high water marks) can be lost on hard kills and restarts

[ https://issues.apache.org/jira/browse/KAFKA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1647: Status: Patch Available (was: Open) > Replication offset checkpoints (high water marks) can be lost

[jira] [Commented] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160503#comment-14160503 ] Guozhang Wang commented on KAFKA-1430: -- Cool. I saw that in the commit log, though th

[jira] [Commented] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160500#comment-14160500 ] Guozhang Wang commented on KAFKA-1430: -- I could go through the changes again, but ks

[jira] [Updated] (KAFKA-1670) Corrupt log files for segment.bytes values close to Int.MaxInt

[ https://issues.apache.org/jira/browse/KAFKA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-1670: -- Attachment: KAFKA-1670_2014-10-06_09:48:25.patch > Corrupt log files for segment

[jira] [Commented] (KAFKA-1670) Corrupt log files for segment.bytes values close to Int.MaxInt

[ https://issues.apache.org/jira/browse/KAFKA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160484#comment-14160484 ] Sriharsha Chintalapani commented on KAFKA-1670: --- Updated reviewboard https:/

Re: Review Request 26346: Patch for KAFKA-1670

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26346/ --- (Updated Oct. 6, 2014, 4:48 p.m.) Review request for kafka. Bugs: KAFKA-1670

Re: [GitHub] kafka pull request: changed List type in RequestPurgatory.Watchers

Hey Michael, Nice catch. We had actually fixed this issue once already, but it looks like the change was lost. Re-opened KAFKA-1430 to track: https://issues.apache.org/jira/browse/KAFKA-1430 -Jay On Mon, Oct 6, 2014 at 7:58 AM, mdykman wrote: > GitHub user mdykman opened a pull request: > >

Re: Review Request 26346: Patch for KAFKA-1670

> On Oct. 5, 2014, 11:35 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/log/Log.scala, line 499 > > > > > > Would it be simpler to just do the following? > > > > if (segment.size + messageSize < (long) con

[jira] [Reopened] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps reopened KAFKA-1430: -- This change reverted KAFKA-1468. That was the issue where we had huge pauses due to using remove() on Array

[jira] [Updated] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1430: - Priority: Blocker (was: Major) > Purgatory redesign > -- > > Key: KAFKA-1

Re: [Java New Producer Kafka Trunk ] Need a State Check API Method

Hey Bhavesh, This is a sanity check. If you send a message after calling close on the producer you should get this error. It sounds like you have multiple threads sending, and you close the producer in the middle of this, then you get this error. This is expected. Perhaps I am misunderstanding?

[jira] [Updated] (KAFKA-1668) TopicCommand doesn't warn if --topic argument doesn't match any topics

[ https://issues.apache.org/jira/browse/KAFKA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1668: - Reviewer: Jay Kreps [~jkreps] Feel free to reassign for review. > TopicCommand doesn't warn if --

Build failed in Jenkins: Kafka-trunk #289

See Changes: [junrao] kafka-1673; potential java.lang.IllegalStateException in BufferPool.allocate(); patched by Jun Rao; reviewed by Jay Kreps -- [...truncated 1694 lines...] kafka.admin.AdminTest

[GitHub] kafka pull request: changed List type in RequestPurgatory.Watchers

GitHub user mdykman opened a pull request: https://github.com/apache/kafka/pull/34 changed List type in RequestPurgatory.Watchers class Watchers is declared, having member private val requests = new util.ArrayList[T] in purgeSatisfied(), an iterator is created

[jira] [Updated] (KAFKA-1673) potential java.lang.IllegalStateException in BufferPool.allocate()

[ https://issues.apache.org/jira/browse/KAFKA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1673: --- Resolution: Fixed Reviewer: Jay Kreps Status: Resolved (was: Patch Available) Thanks for the re

[jira] [Updated] (KAFKA-1674) auto.create.topics.enable docs are misleading

[ https://issues.apache.org/jira/browse/KAFKA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic updated KAFKA-1674: Description: {{auto.create.topics.enable}} is currently [documented|http://kafka.apache.org/08/conf

[jira] [Updated] (KAFKA-1675) bootstrapping tidy-up

[ https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1675: --- Attachment: KAFKA-1675.patch > bootstrapping tidy-up > - > > Key:

Review Request 26362: Patch for KAFKA-1675

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26362/ --- Review request for kafka. Bugs: KAFKA-1675 https://issues.apache.org/jira/b

[jira] [Commented] (KAFKA-1675) bootstrapping tidy-up

[ https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160314#comment-14160314 ] Ivan Lyutov commented on KAFKA-1675: Created reviewboard https://reviews.apache.org/r/

[jira] [Updated] (KAFKA-1675) bootstrapping tidy-up

[ https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1675: --- Status: Patch Available (was: Open) > bootstrapping tidy-up > - > >

[jira] [Updated] (KAFKA-1674) auto.create.topics.enable docs are misleading

[ https://issues.apache.org/jira/browse/KAFKA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic updated KAFKA-1674: Description: {{auto.create.topics.enable}} is currently [documented|http://kafka.apache.org/08/conf

[jira] [Commented] (KAFKA-1671) uploaded archives are missing for Scala version 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160292#comment-14160292 ] Ivan Lyutov commented on KAFKA-1671: Created reviewboard https://reviews.apache.org/r/

[jira] [Updated] (KAFKA-1671) uploaded archives are missing for Scala version 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1671: --- Attachment: KAFKA-1671.patch > uploaded archives are missing for Scala version 2.11 >

[jira] [Updated] (KAFKA-1671) uploaded archives are missing for Scala version 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1671: --- Status: Patch Available (was: Open) > uploaded archives are missing for Scala version 2.11 >

Review Request 26360: Patch for KAFKA-1671

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26360/ --- Review request for kafka. Bugs: KAFKA-1671 https://issues.apache.org/jira/b

[jira] [Updated] (KAFKA-1675) bootstrapping tidy-up

[ https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1675: - Fix Version/s: 0.8.2 Assignee: Ivan Lyutov > bootstrapping tidy-up > - > >

[jira] [Updated] (KAFKA-1644) Inherit FetchResponse from RequestOrResponse

[ https://issues.apache.org/jira/browse/KAFKA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Karamanov updated KAFKA-1644: --- Attachment: 0002-KAFKA-1644-Inherit-FetchResponse-from-RequestOrRespo.patch Maybe it will be O

[jira] [Updated] (KAFKA-1674) auto.create.topics.enable docs are misleading

[ https://issues.apache.org/jira/browse/KAFKA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic updated KAFKA-1674: Description: {{auto.create.topics.enable}} is currently [documented|http://kafka.apache.org/08/conf

[jira] [Assigned] (KAFKA-1671) uploaded archives are missing for Scala version 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov reassigned KAFKA-1671: -- Assignee: Ivan Lyutov > uploaded archives are missing for Scala version 2.11 >

[jira] [Created] (KAFKA-1675) bootstrapping tidy-up

Szczepan Faber created KAFKA-1675: - Summary: bootstrapping tidy-up Key: KAFKA-1675 URL: https://issues.apache.org/jira/browse/KAFKA-1675 Project: Kafka Issue Type: Bug Reporter: S

[jira] [Created] (KAFKA-1674) auto.create.topics.enable docs are misleading

Stevo Slavic created KAFKA-1674: --- Summary: auto.create.topics.enable docs are misleading Key: KAFKA-1674 URL: https://issues.apache.org/jira/browse/KAFKA-1674 Project: Kafka Issue Type: Bug