[jira] [Commented] (KAFKA-3719) Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too narrow

[ https://issues.apache.org/jira/browse/KAFKA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287422#comment-15287422 ] Gwen Shapira commented on KAFKA-3719: - AFAIK, underscores are not legal in hostnames.

[jira] [Commented] (KAFKA-3721) UpdateMetadataRequest V2 should be in API version 0.10.0-IV1

[ https://issues.apache.org/jira/browse/KAFKA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287989#comment-15287989 ] Gwen Shapira commented on KAFKA-3721: - Since we are now releasing - can we modify the

[jira] [Commented] (KAFKA-3721) UpdateMetadataRequest V2 should be in API version 0.10.0-IV1

[ https://issues.apache.org/jira/browse/KAFKA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288003#comment-15288003 ] Gwen Shapira commented on KAFKA-3721: - I think the IV was intended as "intermediate ve

[jira] [Commented] (KAFKA-3721) UpdateMetadataRequest V2 should be in API version 0.10.0-IV1

[ https://issues.apache.org/jira/browse/KAFKA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288017#comment-15288017 ] Gwen Shapira commented on KAFKA-3721: - I guess we had different plans :) At this stag

[jira] [Commented] (KAFKA-3721) UpdateMetadataRequest V2 should be in API version 0.10.0-IV1

[ https://issues.apache.org/jira/browse/KAFKA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288052#comment-15288052 ] Gwen Shapira commented on KAFKA-3721: - I'm ok with whatever [~ijuma] recommends. > Up

[jira] [Created] (KAFKA-3724) Replace inter.broker.protocol.version with KIP-35 based version detection

Gwen Shapira created KAFKA-3724: --- Summary: Replace inter.broker.protocol.version with KIP-35 based version detection Key: KAFKA-3724 URL: https://issues.apache.org/jira/browse/KAFKA-3724 Project: Kafka

[jira] [Updated] (KAFKA-3724) Replace inter.broker.protocol.version with KIP-35 based version detection

[ https://issues.apache.org/jira/browse/KAFKA-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3724: Issue Type: Improvement (was: Bug) > Replace inter.broker.protocol.version with KIP-35 based versio

[jira] [Updated] (KAFKA-175) Add helper scripts to wrap the current perf tools

[ https://issues.apache.org/jira/browse/KAFKA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-175: --- Resolution: Fixed Fix Version/s: (was: 0.10.1.0) Status: Resolved (was: Patch Ava

[jira] [Resolved] (KAFKA-174) Add performance suite for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-174. Resolution: Fixed Fix Version/s: (was: 0.10.1.0) was done ages ago... > Add performance s

[jira] [Resolved] (KAFKA-485) Support MacOS for this test framework

[ https://issues.apache.org/jira/browse/KAFKA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-485. Resolution: Fixed Fix Version/s: (was: 0.10.1.0) related to old test framework which no lo

[jira] [Updated] (KAFKA-1190) create a draw performance graph script

[ https://issues.apache.org/jira/browse/KAFKA-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1190: Resolution: Won't Fix Fix Version/s: (was: 0.10.1.0) Status: Resolved (was: Pa

[jira] [Updated] (KAFKA-1011) Decompression and re-compression on MirrorMaker could result in messages being dropped in the pipeline

[ https://issues.apache.org/jira/browse/KAFKA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1011: Resolution: Fixed Fix Version/s: (was: 0.10.1.0) Status: Resolved (was: Patch

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298900#comment-15298900 ] Gwen Shapira commented on KAFKA-1211: - [~junrao] is this still an issue? > Hold the p

[jira] [Commented] (KAFKA-1573) Transient test failures on LogTest.testCorruptLog

[ https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298901#comment-15298901 ] Gwen Shapira commented on KAFKA-1573: - [~guozhang] is this still failing? > Transient

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299148#comment-15299148 ] Gwen Shapira commented on KAFKA-3370: - actually, it is more complicated... suppose th

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299164#comment-15299164 ] Gwen Shapira commented on KAFKA-3736: - Any reason not to leave this as a github projec

[jira] [Commented] (KAFKA-3737) Closing connection during produce request should be log with WARN level.

[ https://issues.apache.org/jira/browse/KAFKA-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299191#comment-15299191 ] Gwen Shapira commented on KAFKA-3737: - I don't mind bumping up the LOG level, but I do

[jira] [Resolved] (KAFKA-3683) Add file descriptor recommendation to ops guide

[ https://issues.apache.org/jira/browse/KAFKA-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3683. - Resolution: Fixed Fix Version/s: 0.10.0.1 0.10.1.0 Issue resolved by pul

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299252#comment-15299252 ] Gwen Shapira commented on KAFKA-3370: - Not necessarily efficiency - maybe correctness

[jira] [Resolved] (KAFKA-3732) Add an auto accept option to kafka-acls.sh

[ https://issues.apache.org/jira/browse/KAFKA-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3732. - Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request 1406 [https://gith

[jira] [Updated] (KAFKA-3732) Add an auto accept option to kafka-acls.sh

[ https://issues.apache.org/jira/browse/KAFKA-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3732: Assignee: Mickael Maison > Add an auto accept option to kafka-acls.sh >

[jira] [Commented] (KAFKA-2971) KAFKA - Not obeying log4j settings, DailyRollingFileAppender not rolling files

[ https://issues.apache.org/jira/browse/KAFKA-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300723#comment-15300723 ] Gwen Shapira commented on KAFKA-2971: - I don't think [~jkreps] is working on this at t

[jira] [Resolved] (KAFKA-1789) Issue with Async producer

[ https://issues.apache.org/jira/browse/KAFKA-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-1789. - Resolution: Unresolved Unlikely that this will get resolved. > Issue with Async producer > --

[jira] [Updated] (KAFKA-2941) Docs for key/value converter in Kafka connect are unclear

[ https://issues.apache.org/jira/browse/KAFKA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2941: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 15

[jira] [Updated] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3500: Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was: Patch Available)

[jira] [Commented] (KAFKA-3852) Clarify how to handle message format upgrade without killing performance

[ https://issues.apache.org/jira/browse/KAFKA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394990#comment-15394990 ] Gwen Shapira commented on KAFKA-3852: - Hey [~ewencp], mind if I take a crack at that o

[jira] [Commented] (KAFKA-3852) Clarify how to handle message format upgrade without killing performance

[ https://issues.apache.org/jira/browse/KAFKA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394993#comment-15394993 ] Gwen Shapira commented on KAFKA-3852: - ah, I see you just picked it up. Never mind, th

[jira] [Resolved] (KAFKA-3946) Protocol guide should say that Produce request acks can only be 0, 1, or -1

[ https://issues.apache.org/jira/browse/KAFKA-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3946. - Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request 1680 [https://gith

[jira] [Updated] (KAFKA-3847) Connect tasks should not share a producer

[ https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3847: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 17

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102471#comment-14102471 ] Gwen Shapira commented on KAFKA-1400: - No exception is thrown. Thats the problem :) I

[jira] [Commented] (KAFKA-1485) Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run

[ https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102495#comment-14102495 ] Gwen Shapira commented on KAFKA-1485: - Sounds good to me. The first patch attached to

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103285#comment-14103285 ] Gwen Shapira commented on KAFKA-1400: - Good idea. Will do that next time the issue rep

[jira] [Commented] (KAFKA-1485) Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run

[ https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106029#comment-14106029 ] Gwen Shapira commented on KAFKA-1485: - Agree about the many bug fixes in 3.4.6. Howeve

[jira] [Assigned] (KAFKA-1548) Refactor the "replica_id" in requests

[ https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-1548: --- Assignee: Gwen Shapira > Refactor the "replica_id" in requests >

[jira] [Commented] (KAFKA-1548) Refactor the "replica_id" in requests

[ https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106238#comment-14106238 ] Gwen Shapira commented on KAFKA-1548: - I think the name replica_id is fine. For #2,

[jira] [Commented] (KAFKA-1489) Global threshold on data retention size

[ https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106257#comment-14106257 ] Gwen Shapira commented on KAFKA-1489: - I still don't see how "global retention size" w

[jira] [Commented] (KAFKA-1486) Move all request/responses to use schema-utils

[ https://issues.apache.org/jira/browse/KAFKA-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106262#comment-14106262 ] Gwen Shapira commented on KAFKA-1486: - [~raulcf] - mind if I pick this one? > Move al

[jira] [Resolved] (KAFKA-1177) DeleteTopics gives Successful message even if the specified Topic is not present

[ https://issues.apache.org/jira/browse/KAFKA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-1177. - Resolution: Fixed Following KAFKA-1443 and KAFKA-1576, this should be resolved. > DeleteTopics g

[jira] [Assigned] (KAFKA-1486) Move all request/responses to use schema-utils

[ https://issues.apache.org/jira/browse/KAFKA-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-1486: --- Assignee: Gwen Shapira > Move all request/responses to use schema-utils > ---

[jira] [Commented] (KAFKA-1489) Global threshold on data retention size

[ https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106287#comment-14106287 ] Gwen Shapira commented on KAFKA-1489: - Thanks for clarifying! The issue description sa

[jira] [Commented] (KAFKA-1486) Move all request/responses to use schema-utils

[ https://issues.apache.org/jira/browse/KAFKA-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107167#comment-14107167 ] Gwen Shapira commented on KAFKA-1486: - Thanks [~guozhang]. If I understand you (and t

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

[ https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108781#comment-14108781 ] Gwen Shapira commented on KAFKA-1419: - Its not binary, it is ucs-2. After iconv (icon

[jira] [Commented] (KAFKA-1489) Global threshold on data retention size

[ https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109350#comment-14109350 ] Gwen Shapira commented on KAFKA-1489: - I actually like the idea of configuring max byt

[jira] [Updated] (KAFKA-1485) Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run

[ https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1485: Attachment: KAFKA-1485.4.patch Patch for ZK 3.4.6 with a wrapper class for ZooKeeperMain that allow

[jira] [Created] (KAFKA-1611) Improve system test configuration

Gwen Shapira created KAFKA-1611: --- Summary: Improve system test configuration Key: KAFKA-1611 URL: https://issues.apache.org/jira/browse/KAFKA-1611 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-1611) Improve system test configuration

[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1611: Status: Patch Available (was: Open) > Improve system test configuration >

[jira] [Updated] (KAFKA-1611) Improve system test configuration

[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1611: Attachment: KAFKA-1611.0.patch Fixed the hardcoded java_home issue and added support for JAVA_HOME

[jira] [Commented] (KAFKA-1611) Improve system test configuration

[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110020#comment-14110020 ] Gwen Shapira commented on KAFKA-1611: - Once this is committed, I'll add a note about J

[jira] [Created] (KAFKA-1613) Improve system test documentation

Gwen Shapira created KAFKA-1613: --- Summary: Improve system test documentation Key: KAFKA-1613 URL: https://issues.apache.org/jira/browse/KAFKA-1613 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-1611) Improve system test configuration

[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110065#comment-14110065 ] Gwen Shapira commented on KAFKA-1611: - [~guozhang] and [~joestein]: Pinging for review

[jira] [Commented] (KAFKA-1612) Consumer offsets auto-commit before processing finishes

[ https://issues.apache.org/jira/browse/KAFKA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110100#comment-14110100 ] Gwen Shapira commented on KAFKA-1612: - You should be able to use the commitOffsets() A

[jira] [Commented] (KAFKA-934) kafka hadoop consumer and producer use older 0.19.2 hadoop api's

[ https://issues.apache.org/jira/browse/KAFKA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112505#comment-14112505 ] Gwen Shapira commented on KAFKA-934: Are we still maintaining those? I thought these w

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112529#comment-14112529 ] Gwen Shapira commented on KAFKA-1555: - I agree that min.isr only makes sense with ack=

[jira] [Created] (KAFKA-1615) Generating group ID in ZookeeperConsumerConnector shouldn't require local hostname to resolve

Gwen Shapira created KAFKA-1615: --- Summary: Generating group ID in ZookeeperConsumerConnector shouldn't require local hostname to resolve Key: KAFKA-1615 URL: https://issues.apache.org/jira/browse/KAFKA-1615

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

Gwen Shapira created KAFKA-1618: --- Summary: Exception thrown when running console producer with no port number for the broker Key: KAFKA-1618 URL: https://issues.apache.org/jira/browse/KAFKA-1618 Project

[jira] [Assigned] (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:all-tabpanel ] Gwen Shapira reassigned KAFKA-1618: --- Assignee: Gwen Shapira > Exception thrown when running console producer with no port number f

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120815#comment-14120815 ] Gwen Shapira commented on KAFKA-1555: - If there's a consensus (or even a lazy consensu

[jira] [Reopened] (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:all-tabpanel ] Gwen Shapira reopened KAFKA-1618: - Re-openning, since AFAIK, the patch is not committed yet. > Exception thrown when running console pro

[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=14123632#comment-14123632 ] Gwen Shapira commented on KAFKA-1618: - [~balaji.sesha...@dish.com] - per Joe's comment

[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=14129506#comment-14129506 ] Gwen Shapira commented on KAFKA-1558: - I don't think the issue as described above exis

[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=14134813#comment-14134813 ] Gwen Shapira commented on KAFKA-1618: - I still think that using port 9092 as default m

[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=14136362#comment-14136362 ] Gwen Shapira commented on KAFKA-1618: - I can't think of other client server system tha

[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.0.patch Tested the change with a 3-broker cluster. Taking one broker down to

[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.1.patch Sorry, first patch was missing a file. > provide strong consistency

[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: Status: Patch Available (was: Open) > provide strong consistency with reasonable availability > ---

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143352#comment-14143352 ] Gwen Shapira commented on KAFKA-1555: - Hi Sriram, Thank you for raising these concern

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143501#comment-14143501 ] Gwen Shapira commented on KAFKA-1555: - There is a review board (https://reviews.apache

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143600#comment-14143600 ] Gwen Shapira commented on KAFKA-1555: - [~sriramsub] 2..N-1: We want to be sure writes

[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.2.patch > provide strong consistency with reasonable availability > -

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144101#comment-14144101 ] Gwen Shapira commented on KAFKA-1555: - Uploaded an updated patch addressing [~joestein

[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.3.patch Removed the warning from appendToLocalLog since the exception won't g

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144999#comment-14144999 ] Gwen Shapira commented on KAFKA-1555: - [~joestein] can you share your producer configu

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14145077#comment-14145077 ] Gwen Shapira commented on KAFKA-1477: - Quick question regarding the patch: In the wiki

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14145090#comment-14145090 ] Gwen Shapira commented on KAFKA-1477: - Another question: The change mentions that the

[jira] [Commented] (KAFKA-1611) Improve system test configuration

[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145137#comment-14145137 ] Gwen Shapira commented on KAFKA-1611: - Updated wiki. Mentioned JAVA_HOME in quickstart

[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.4.patch > provide strong consistency with reasonable availability > -

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147394#comment-14147394 ] Gwen Shapira commented on KAFKA-1555: - +1 for dropping ack > 1 The whole Jira started

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147395#comment-14147395 ] Gwen Shapira commented on KAFKA-1555: - Also, attached a version of the patch with few

[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.5.patch Noticed that prev patch accidentally included my slightly modified b

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

[ https://issues.apache.org/jira/browse/KAFKA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148450#comment-14148450 ] Gwen Shapira commented on KAFKA-1555: - Call me a control freak, but "don't lose data"

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151264#comment-14151264 ] Gwen Shapira commented on KAFKA-1387: - AFAIK the ZK bug was never reproduced in newer

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151275#comment-14151275 ] Gwen Shapira commented on KAFKA-1387: - ZOOKEEPER-1809 was closed because the re-creati

[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.5.patch Uploaded latest version. Addressing the duplicates and the acks>1 is

[jira] [Updated] (KAFKA-294) "Path length must be > 0" error during startup

[ https://issues.apache.org/jira/browse/KAFKA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-294: --- Fix Version/s: 0.8.2 > "Path length must be > 0" error during startup > ---

[jira] [Resolved] (KAFKA-294) "Path length must be > 0" error during startup

[ https://issues.apache.org/jira/browse/KAFKA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-294. Resolution: Fixed With KAFKA-404 committed, this is resolved too. > "Path length must be > 0" error

[jira] [Assigned] (KAFKA-1664) Kafka does not properly parse multiple ZK nodes with non-root chroot

[ https://issues.apache.org/jira/browse/KAFKA-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-1664: --- Assignee: Gwen Shapira > Kafka does not properly parse multiple ZK nodes with non-root chroot

[jira] [Commented] (KAFKA-1664) Kafka does not properly parse multiple ZK nodes with non-root chroot

[ https://issues.apache.org/jira/browse/KAFKA-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155704#comment-14155704 ] Gwen Shapira commented on KAFKA-1664: - This happens with other high-level consumer cli

[jira] [Comment Edited] (KAFKA-1664) Kafka does not properly parse multiple ZK nodes with non-root chroot

[ https://issues.apache.org/jira/browse/KAFKA-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155704#comment-14155704 ] Gwen Shapira edited comment on KAFKA-1664 at 10/1/14 10:43 PM: -

[jira] [Commented] (KAFKA-1664) Kafka does not properly parse multiple ZK nodes with non-root chroot

[ https://issues.apache.org/jira/browse/KAFKA-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157228#comment-14157228 ] Gwen Shapira commented on KAFKA-1664: - For a more meaningful error, I'm thinking: Catc

[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] [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] [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

[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-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] [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] [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.8.patch rebased on trunk > provide strong consistency with reasonable availa

[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.9.patch > provide strong consistency with reasonable availability > -

[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=14166146#comment-14166146 ] Gwen Shapira commented on KAFKA-1696: - The way Hadoop currently works, MapReduce tasks

[jira] [Assigned] (KAFKA-1697) remove code related to ack>1 on the broker

[ https://issues.apache.org/jira/browse/KAFKA-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-1697: --- Assignee: Gwen Shapira > remove code related to ack>1 on the broker > ---

[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=14166364#comment-14166364 ] Gwen Shapira commented on KAFKA-1696: - Since the delegation tokens depend on SASL/MD5-

<    9   10   11   12   13   14   15   16   17   >