[jira] [Created] (KAFKA-1640) consumer will fail if encounter special offset

chenshangan created KAFKA-1640: -- Summary: consumer will fail if encounter special offset Key: KAFKA-1640 URL: https://issues.apache.org/jira/browse/KAFKA-1640 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1640) consumer will fail if encounter special offset

[ https://issues.apache.org/jira/browse/KAFKA-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138733#comment-14138733 ] chenshangan commented on KAFKA-1640: The following is about the test: offset info wit

Re: Review Request 22131: Patch for KAFKA-1477

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22131/ --- (Updated Sept. 18, 2014, 12:43 p.m.) Review request for kafka. Bugs: KAFKA-14

[jira] [Updated] (KAFKA-1477) add authentication layer and initial JKS x509 implementation for brokers, producers and consumer for network communication

[ https://issues.apache.org/jira/browse/KAFKA-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1477: --- Attachment: KAFKA-1477_trunk.patch Updated patch to current trunk > add authentication layer and init

[jira] [Updated] (KAFKA-1419) cross build for scala 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1419: --- Attachment: KAFKA-1419_cross_build_for_scala_2_11_for_0_8_1_branch.patch Added the same patch for 0.8.

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138972#comment-14138972 ] Neha Narkhede commented on KAFKA-1282: -- Thanks for the updated patch. Overall, looks

[jira] [Commented] (KAFKA-1558) AdminUtils.deleteTopic does not work

[ https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138979#comment-14138979 ] Neha Narkhede commented on KAFKA-1558: -- [~sriharsha] Delete topic shouldn't be affect

[jira] [Commented] (KAFKA-1558) AdminUtils.deleteTopic does not work

[ https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139025#comment-14139025 ] Sriharsha Chintalapani commented on KAFKA-1558: --- [~nehanarkhede] Should we a

[jira] [Commented] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139038#comment-14139038 ] BalajiSeshadri commented on KAFKA-1618: --- [~nehanarkhede] I submitted patch(KAFKA-161

[jira] [Commented] (KAFKA-1640) consumer will fail if encounter special offset

[ https://issues.apache.org/jira/browse/KAFKA-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139142#comment-14139142 ] Guozhang Wang commented on KAFKA-1640: -- Can you turn on log4j on the consumer is see

[jira] [Commented] (KAFKA-1591) Clean-up Unnecessary stack trace in error/warn logs

[ https://issues.apache.org/jira/browse/KAFKA-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139192#comment-14139192 ] Guozhang Wang commented on KAFKA-1591: -- Thanks for the patch, a few more comments bel

[jira] [Resolved] (KAFKA-1592) Some INFO level logging needs to be DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat resolved KAFKA-1592. Resolution: Duplicate Reviewer: Guozhang Wang Closing a duplicate as the changes were

[jira] [Updated] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicu marasoiu updated KAFKA-1282: - Attachment: 1282_brush.patch attached, renamed time and for the "initial/reset value of the nextId

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139513#comment-14139513 ] Jun Rao commented on KAFKA-1282: Do you think you can reproduce that data loss issue in 1

[jira] [Commented] (KAFKA-1123) Broker IPv6 addresses parsed incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139537#comment-14139537 ] Jun Rao commented on KAFKA-1123: Thanks for the latest patch. In Broker, you used the simp

[jira] [Updated] (KAFKA-1123) Broker IPv6 addresses parsed incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Szafrański updated KAFKA-1123: Attachment: KAFKA-1123_v4.patch I have now removed the string interpolation syntax.

[jira] [Updated] (KAFKA-1123) Broker IPv6 addresses parsed incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1123: --- Resolution: Fixed Fix Version/s: 0.8.2 Assignee: Krzysztof Szafrański Status: Resolv

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

Joel Koshy created KAFKA-1641: - Summary: Log cleaner exits if last cleaned offset is lower than earliest offset Key: KAFKA-1641 URL: https://issues.apache.org/jira/browse/KAFKA-1641 Project: Kafka

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

See

[jira] [Commented] (KAFKA-1640) consumer will fail if encounter special offset

[ https://issues.apache.org/jira/browse/KAFKA-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139928#comment-14139928 ] chenshangan commented on KAFKA-1640: [~guozhang] thanks for you suggestion, it's beca

[jira] [Resolved] (KAFKA-1640) consumer will fail if encounter special offset

[ https://issues.apache.org/jira/browse/KAFKA-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenshangan resolved KAFKA-1640. Resolution: Not a Problem > consumer will fail if encounter special offset > ---

[jira] [Created] (KAFKA-1642) [Java New Producer Kafka Trunk] CPU Usage Spike to 100% when network connection is lost

Bhavesh Mistry created KAFKA-1642: - Summary: [Java New Producer Kafka Trunk] CPU Usage Spike to 100% when network connection is lost Key: KAFKA-1642 URL: https://issues.apache.org/jira/browse/KAFKA-1642

[jira] [Updated] (KAFKA-1591) Clean-up Unnecessary stack trace in error/warn logs

[ https://issues.apache.org/jira/browse/KAFKA-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Sharma updated KAFKA-1591: --- Attachment: Jira-1591- As per Guozhang latest comment.patch Contains combined one patch file -