[jira] [Updated] (KAFKA-1509) Restart of destination broker after unreplicated partition move leaves partitions without leader

[ https://issues.apache.org/jira/browse/KAFKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Strasheim updated KAFKA-1509: Summary: Restart of destination broker after unreplicated partition move leaves partitions

[jira] [Comment Edited] (KAFKA-1509) Restart of destination broker after partition move leaves partitions without leader

[ https://issues.apache.org/jira/browse/KAFKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045497#comment-14045497 ] Albert Strasheim edited comment on KAFKA-1509 at 6/27/14 4:04 AM: --

[jira] [Commented] (KAFKA-1509) Restart of destination broker after partition move leaves partitions without leader

[ https://issues.apache.org/jira/browse/KAFKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045497#comment-14045497 ] Albert Strasheim commented on KAFKA-1509: - Workaround: patch up all the /brokers/t

[jira] [Updated] (KAFKA-1509) Restart of destination broker after partition move leaves partitions without leader

[ https://issues.apache.org/jira/browse/KAFKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Strasheim updated KAFKA-1509: Attachment: controller2.log controller log. I tried a bunch of things (partition assignment

[jira] [Commented] (KAFKA-1507) Using GetOffsetShell against non-existent topic creates the topic unintentionally

[ https://issues.apache.org/jira/browse/KAFKA-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045422#comment-14045422 ] Sriharsha Chintalapani commented on KAFKA-1507: --- [~nehanarkhede] this is th

Re: Review Request 22905: Patch for KAFKA-1477

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22905/ --- (Updated June 27, 2014, 1:22 a.m.) Review request for kafka. Repository: kafk

Re: Review Request 22905: Patch for KAFKA-1477

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22905/ --- (Updated June 27, 2014, 1:20 a.m.) Review request for kafka. Repository: kafk

Apache Kafka NYC Users Group!

Hi folks, I just started a new Meetup specifically for Apache Kafka in NYC (everyone is welcome of course) http://www.meetup.com/Apache-Kafka-NYC/ For the last couple of years we have been piggy backing talks and the community with other NYC meetup groups (Storm, Cassandra, Hadoop, etc) and figure

[jira] [Commented] (KAFKA-1509) Restart of destination broker after partition move leaves partitions without leader

[ https://issues.apache.org/jira/browse/KAFKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045360#comment-14045360 ] Guozhang Wang commented on KAFKA-1509: -- Could you check if there is any exceptions/er

Re: Review Request 22905: Patch for KAFKA-1477

> On June 26, 2014, 12:51 a.m., Joel Koshy wrote: > > core/src/main/scala/kafka/api/RequestKeys.scala, line 36 > > > > > > Just wondering if TransactionMetadata is misleading - since we are > > actually inquiring about

[jira] [Created] (KAFKA-1509) Restart of destination broker after partition move leaves partitions without leader

Albert Strasheim created KAFKA-1509: --- Summary: Restart of destination broker after partition move leaves partitions without leader Key: KAFKA-1509 URL: https://issues.apache.org/jira/browse/KAFKA-1509

[jira] [Resolved] (KAFKA-1096) An old controller coming out of long GC could update its epoch to the latest controller's epoch

[ https://issues.apache.org/jira/browse/KAFKA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-1096. -- Resolution: Fixed Thanks for the updated patch! Pushed to trunk > An old controller coming out

Re: Review Request 22496: Patch for KAFKA-1096

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22496/#review46809 --- Ship it! Ship It! - Neha Narkhede On June 20, 2014, 10:27 p.m.,

[jira] [Resolved] (KAFKA-1504) Replica is unable to update ISR

[ https://issues.apache.org/jira/browse/KAFKA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-1504. -- Resolution: Not a Problem Please retry the test on trunk as [~guozhang] suggested since the fix

[jira] [Closed] (KAFKA-1504) Replica is unable to update ISR

[ https://issues.apache.org/jira/browse/KAFKA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-1504. Assignee: (was: Neha Narkhede) > Replica is unable to update ISR >

[jira] [Comment Edited] (KAFKA-1504) Replica is unable to update ISR

[ https://issues.apache.org/jira/browse/KAFKA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045268#comment-14045268 ] Neha Narkhede edited comment on KAFKA-1504 at 6/26/14 10:21 PM:

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (97 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-1503 all partitions are using same broker as their leader after broker is down https://issues.apache.org/jira/browse/KAFKA-1

Re: Review Request 22841: Patch for KAFKA-1329

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22841/#review46769 --- clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerCon

[jira] [Commented] (KAFKA-1503) all partitions are using same broker as their leader after broker is down

[ https://issues.apache.org/jira/browse/KAFKA-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044879#comment-14044879 ] Guozhang Wang commented on KAFKA-1503: -- Looks good to me. [~junrao] Could you take a

Re: Review Request 22874: Fix KAFKA-1498

> On June 26, 2014, 4:57 a.m., Jay Kreps wrote: > > clients/src/main/java/org/apache/kafka/clients/producer/internals/RecordAccumulator.java, > > line 76 > > > > > > I don't understand this parameter. Explained above.