[jira] [Commented] (KAFKA-1646) Improve consumer read performance for Windows

[ https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179731#comment-14179731 ] xueqiang wang commented on KAFKA-1646: -- Hey, Jay, sorry for late. I have done a test

[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 ] Joe Stein reassigned KAFKA-1678: Assignee: Dmitry Pekar (was: Gwen Shapira) > add new options for reassign partition to better mana

[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: - Component/s: tools > 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: Four changes here each requiring system test, unit test, code to-do the actual work and we s

[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: Four changes here each requiring a) system tests b) unit test c) code to-do the actual work

[jira] [Commented] (KAFKA-1481) Stop using dashes AND underscores as separators in MBean names

[ https://issues.apache.org/jira/browse/KAFKA-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179935#comment-14179935 ] Otis Gospodnetic commented on KAFKA-1481: - [~junrao] - in interest of getting this

[jira] [Commented] (KAFKA-1716) hang during shutdown of ZookeeperConsumerConnector

[ https://issues.apache.org/jira/browse/KAFKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179980#comment-14179980 ] Chris Richardson commented on KAFKA-1716: - All of my ConsumerFetcherThreads look l

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180033#comment-14180033 ] Guozhang Wang commented on KAFKA-1718: -- Since the reason we add the "max.message.size

[jira] [Commented] (KAFKA-1583) Kafka API Refactoring

[ https://issues.apache.org/jira/browse/KAFKA-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180037#comment-14180037 ] Guozhang Wang commented on KAFKA-1583: -- Yes, the system tests without the offset mana

[jira] [Commented] (KAFKA-1481) Stop using dashes AND underscores as separators in MBean names

[ https://issues.apache.org/jira/browse/KAFKA-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180056#comment-14180056 ] Jun Rao commented on KAFKA-1481: Otis, I expect that we will have about another 4 weeks b

[jira] [Comment Edited] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180126#comment-14180126 ] Evan Huus edited comment on KAFKA-1718 at 10/22/14 4:22 PM: ??

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180126#comment-14180126 ] Evan Huus commented on KAFKA-1718: -- ??when it gets a partial message from the broker it w

[jira] [Assigned] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned KAFKA-1686: - Assignee: Sriharsha Chintalapani > Implement SASL/Kerberos >

[jira] [Assigned] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned KAFKA-1696: - Assignee: Sriharsha Chintalapani > Kafka should be able to generate Hadoo

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180140#comment-14180140 ] Sriharsha Chintalapani commented on KAFKA-1696: --- [~gwenshap] Incase if you n

[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=14180148#comment-14180148 ] Neha Narkhede commented on KAFKA-1647: -- [~noslowerdna] This is pretty corner case and

Documentation with patches

This comes up a lot but in reality not enough. We don't have a great way for folks to modify the code and change (or add) to the documentation. I think the documentation is awesome and as we grow the code contributors that should continue with them too. One thought I had that would work is that w

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180160#comment-14180160 ] Gwen Shapira commented on KAFKA-1696: - I started on the design doc, but I'll admit tha

Re: Review Request 26666: Patch for KAFKA-1653

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2/#review57817 --- Ship it! Ship It! - Neha Narkhede On Oct. 21, 2014, 6:58 p.m., E

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180165#comment-14180165 ] Sriharsha Chintalapani commented on KAFKA-1696: --- [~gwenshap] sounds good to

[jira] [Updated] (KAFKA-1653) Duplicate broker ids allowed in replica assignment

[ https://issues.apache.org/jira/browse/KAFKA-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1653: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patches. Pushed

[jira] [Updated] (KAFKA-1653) Duplicate broker ids allowed in replica assignment

[ https://issues.apache.org/jira/browse/KAFKA-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1653: - Fix Version/s: 0.8.2 > Duplicate broker ids allowed in replica assignment > --

[jira] [Closed] (KAFKA-1653) Duplicate broker ids allowed in replica assignment

[ https://issues.apache.org/jira/browse/KAFKA-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-1653. > Duplicate broker ids allowed in replica assignment > -

[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=14180181#comment-14180181 ] Jiangjie Qin commented on KAFKA-1647: - [~nehanarkhede] I haven't got a chance to do te

Re: Documentation with patches

Hey Joe, I'd love to encourage documentation contributions. I think we do have a way to contribute to docs. The current workflow for contributing is 1. Checkout the docs 2. Change docs 3. Submit patch in normal way 4. Committer reviews and applies For committers we have traditionally made the re

Re: Documentation with patches

I would strongly support this idea. We have similar model in all other projects where I’m involved: The docs are part of the usual code base and we do require contributors to update them when they are adding a new feature. And then during release time we simply take snapshot of the docs and upl

[jira] [Assigned] (KAFKA-1688) Add authorization interface and naive implementation

[ https://issues.apache.org/jira/browse/KAFKA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned KAFKA-1688: - Assignee: Sriharsha Chintalapani > Add authorization interface and naive

[jira] [Commented] (KAFKA-1688) Add authorization interface and naive implementation

[ https://issues.apache.org/jira/browse/KAFKA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180227#comment-14180227 ] Sriharsha Chintalapani commented on KAFKA-1688: --- [~jkreps] Can you please as

Re: Documentation with patches

Currently we are handling the versioning problem by explicitly versioning docs that change over time (configuration, quickstart, design, etc). This is done by just creating a copy of these pages for each release in a subdirectory. So we can commit documentation changes at any time for the future re

Re: Review Request 26373: Patch for KAFKA-1647

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26373/#review57836 --- core/src/main/scala/kafka/server/ReplicaManager.scala

[jira] [Created] (KAFKA-1724) Errors after reboot in single node setup

Ciprian Hacman created KAFKA-1724: - Summary: Errors after reboot in single node setup Key: KAFKA-1724 URL: https://issues.apache.org/jira/browse/KAFKA-1724 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-1724) Errors after reboot in single node setup

[ https://issues.apache.org/jira/browse/KAFKA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned KAFKA-1724: - Assignee: Sriharsha Chintalapani > Errors after reboot in single node set

[jira] [Updated] (KAFKA-1724) Errors after reboot in single node setup

[ https://issues.apache.org/jira/browse/KAFKA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ciprian Hacman updated KAFKA-1724: -- Fix Version/s: 0.8.2 > Errors after reboot in single node setup > --

[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=14180328#comment-14180328 ] Joel Koshy commented on KAFKA-1647: --- [~becket_qin] here are some steps to reproduce loca

Mirror Maker upgraded to use Java Producer

Hi Kafka Dev Team, In trunk branch, is MM maker upgraded to use new Producer Code Base ? I just wanted to know if this is in plan or already done ? Thanks, Bhavesh

[jira] [Commented] (KAFKA-1695) Authenticate connection to Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180538#comment-14180538 ] Gwen Shapira commented on KAFKA-1695: - The good news is that Kafka works out of the bo

Re: Review Request 26994: Patch for KAFKA-1719

> On Oct. 21, 2014, 10:21 p.m., Guozhang Wang wrote: > > core/src/main/scala/kafka/tools/MirrorMaker.scala, line 323 > > > > > > Is this change intended? Yes, it is intended, so that we can make sure each data channel

Re: Review Request 26994: Patch for KAFKA-1719

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26994/#review57907 --- core/src/main/scala/kafka/tools/MirrorMaker.scala

Re: Mirror Maker upgraded to use Java Producer

It is available through the --new.producer option. On Wed, Oct 22, 2014 at 2:05 PM, Bhavesh Mistry wrote: > Hi Kafka Dev Team, > > In trunk branch, is MM maker upgraded to use new Producer Code Base ? I > just wanted to know if this is in plan or already done ? > > > Thanks, > > Bhavesh >

[jira] [Updated] (KAFKA-1724) Errors after reboot in single node setup

[ https://issues.apache.org/jira/browse/KAFKA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1724: - Labels: newbie (was: ) > Errors after reboot in single node setup > -

[jira] [Commented] (KAFKA-1695) Authenticate connection to Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180572#comment-14180572 ] Gwen Shapira commented on KAFKA-1695: - I left a note on the ZKClient pull request. If

Re: Review Request 26994: Patch for KAFKA-1719

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26994/ --- (Updated Oct. 22, 2014, 10:04 p.m.) Review request for kafka. Bugs: KAFKA-171

[jira] [Commented] (KAFKA-1719) Make mirror maker exit when one consumer/producer thread exits.

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

[jira] [Updated] (KAFKA-1719) Make mirror maker exit when one consumer/producer thread exits.

[ https://issues.apache.org/jira/browse/KAFKA-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1719: Attachment: KAFKA-1719_2014-10-22_15:04:32.patch > Make mirror maker exit when one consumer/producer

Re: Mirror Maker upgraded to use Java Producer

Hi Neha, Thank you for this information. Thanks, Bhavesh On Wed, Oct 22, 2014 at 2:34 PM, Neha Narkhede wrote: > It is available through the --new.producer option. > > > On Wed, Oct 22, 2014 at 2:05 PM, Bhavesh Mistry < > mistry.p.bhav...@gmail.com> > wrote: > > > Hi Kafka Dev Team, > > > > I

[jira] [Created] (KAFKA-1725) Configuration file bugs in system tests add noise to output and break a few tests

Ewen Cheslack-Postava created KAFKA-1725: Summary: Configuration file bugs in system tests add noise to output and break a few tests Key: KAFKA-1725 URL: https://issues.apache.org/jira/browse/KAFKA-1725

Review Request 27060: Patch for KAFKA-1725

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

[jira] [Updated] (KAFKA-1725) Configuration file bugs in system tests add noise to output and break a few tests

[ https://issues.apache.org/jira/browse/KAFKA-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-1725: - Attachment: KAFKA-1725.patch > Configuration file bugs in system tests add noise t

[jira] [Updated] (KAFKA-1725) Configuration file bugs in system tests add noise to output and break a few tests

[ https://issues.apache.org/jira/browse/KAFKA-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-1725: - Status: Patch Available (was: Open) > Configuration file bugs in system tests add

[jira] [Commented] (KAFKA-1725) Configuration file bugs in system tests add noise to output and break a few tests

[ https://issues.apache.org/jira/browse/KAFKA-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180753#comment-14180753 ] Ewen Cheslack-Postava commented on KAFKA-1725: -- Created reviewboard https://r

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180763#comment-14180763 ] Guozhang Wang commented on KAFKA-1718: -- Yes, that is what I was thinking about. > "M

Re: Review Request 26373: Patch for KAFKA-1647

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26373/#review57947 --- core/src/main/scala/kafka/server/ReplicaManager.scala

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180856#comment-14180856 ] Jun Rao commented on KAFKA-1718: [~guozhang], removing the max message size may be a bigge

Re: Review Request 24676: Fix KAFKA-1583

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24676/ --- (Updated Oct. 23, 2014, 1:53 a.m.) Review request for kafka. Summary (updated

[jira] [Updated] (KAFKA-1583) Kafka API Refactoring

[ https://issues.apache.org/jira/browse/KAFKA-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1583: - Attachment: KAFKA-1583_2014-10-22_18:52:52.patch > Kafka API Refactoring > - >

[jira] [Commented] (KAFKA-1583) Kafka API Refactoring

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

Re: Review Request 24676: Fix KAFKA-1583

> On Oct. 22, 2014, 1:46 a.m., Joel Koshy wrote: > > core/src/main/scala/kafka/cluster/Partition.scala, line 245 > > > > > > Maybe use this: > > "Recorded replica %d log end offset (LEO)..." > > > > Also,

Re: Review Request 26994: Patch for KAFKA-1719

> On Oct. 22, 2014, 9:32 p.m., Neha Narkhede wrote: > > core/src/main/scala/kafka/tools/MirrorMaker.scala, line 271 > > > > > > Is there any value in setting this to true? It seems that just checking > > if it is fals

[jira] [Commented] (KAFKA-1683) Implement a "session" concept in the socket server

[ https://issues.apache.org/jira/browse/KAFKA-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180983#comment-14180983 ] Gwen Shapira commented on KAFKA-1683: - We need to map SelectorKeys (representing conne

[jira] [Assigned] (KAFKA-1687) SASL tests

[ https://issues.apache.org/jira/browse/KAFKA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-1687: --- Assignee: Gwen Shapira > SASL tests > -- > > Key: KAFKA-1687 >

[jira] [Commented] (KAFKA-1687) SASL tests

[ https://issues.apache.org/jira/browse/KAFKA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181037#comment-14181037 ] Gwen Shapira commented on KAFKA-1687: - Picked it up so this will have an owner. This i