[jira] [Commented] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823291#comment-13823291 ] Jun Rao commented on KAFKA-1112: The following is my confusion. The patch relies on a pot

Some Kafka conversation going on at HN right now...

https://news.ycombinator.com/item?id=6734381

Re: Review Request 15503: Patch for KAFKA-1131

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15503/#review28903 --- Ship it! Ship It! - Neha Narkhede On Nov. 14, 2013, 12:49 a.m.,

[jira] [Updated] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1112: - Attachment: KAFKA-1112-v2.patch Added a new patch that addresses issues raised. Jun 1. I don't think thi

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (75 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-1131 copy some more files into the release tar and zip that are needed/desired https://issues.apache.org/jira/browse/KAFKA-1

Re: Review Request 15201: address all review comments

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15201/#review28873 --- Ship it! Ship It! - Swapnil Ghike On Nov. 14, 2013, 4:24 p.m., J

Re: Review Request 15201: address all review comments

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15201/#review28872 --- Ship it! Ship It! - Guozhang Wang On Nov. 14, 2013, 4:24 p.m., J

[jira] [Updated] (KAFKA-1117) tool for checking the consistency among replicas

[ https://issues.apache.org/jira/browse/KAFKA-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1117: --- Attachment: KAFKA-1117_2013-11-14_08:24:41.patch > tool for checking the consistency among replicas > ---

[jira] [Commented] (KAFKA-1117) tool for checking the consistency among replicas

[ https://issues.apache.org/jira/browse/KAFKA-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822568#comment-13822568 ] Jun Rao commented on KAFKA-1117: Updated reviewboard https://reviews.apache.org/r/15201/

Re: Review Request 15201: address all review comments

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15201/ --- (Updated Nov. 14, 2013, 4:24 p.m.) Review request for kafka. Summary (updated

Re: Review Request 15201: address more review comments

> On Nov. 13, 2013, 2:09 a.m., Joel Koshy wrote: > > Looks good overall - this is definitely a useful tool to have. I'm posting > > comments so far but I will come back to it tomorrow to finish up. > > > > So what would be the recommended procedure when the tool reports an > > inconsistency? W

Re: Review Request 15201: address more review comments

> On Nov. 13, 2013, 7:43 a.m., Swapnil Ghike wrote: > > core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala, line 70 > > > > > > fetchsize -> fetch-size for consistency with other options? changed. > On Nov

[jira] [Commented] (KAFKA-1124) Sending to a new topic (with auto.create.topics.enable) returns ERROR

[ https://issues.apache.org/jira/browse/KAFKA-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822488#comment-13822488 ] Jason Rosenberg commented on KAFKA-1124: [~anujmehta] are you looking in the logs

Errors in the Kafka by-laws

Hello, Your bylaws have an erroneous definition of lazy consensus: > Lazy consensus requires 3 binding +1 votes and no binding vetoes. Lazy consensus is "silence is consent", and requires no +1 votes. The correct term for what your by-laws describe here is consensus approval. The Apache Hadoop

Re: Auto create "chroot" on server start up?

I don't think its too much to ask people to create their ZK paths: zkCli.sh -server localhost:2181 create /kafka kafka Asking a ZK application to use a non-existent chroot is like asking tar to extract to a non-existent directory. An error is appropriate. I think the fix here is to give a bett