[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189472#comment-14189472 ] Jay Kreps commented on KAFKA-1501: -- Interesting. There is an inherent race condition in

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186879#comment-14186879 ] Jay Kreps commented on KAFKA-1501: -- It might be worth checking out that stack overflow

[jira] [Commented] (KAFKA-1736) Improve parition-broker assignment strategy for better availaility in majority durability modes

[ https://issues.apache.org/jira/browse/KAFKA-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14187701#comment-14187701 ] Jay Kreps commented on KAFKA-1736: -- Yes, this is correct. This is a common tradeoff in

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186130#comment-14186130 ] Jay Kreps commented on KAFKA-1501: -- Nice, so statistically it is 93% likely to be fixed,

[jira] [Commented] (KAFKA-1710) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183514#comment-14183514 ] Jay Kreps commented on KAFKA-1710: -- Ah, gotcha, so that was per ms not per us. Question

[jira] [Commented] (KAFKA-1710) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183545#comment-14183545 ] Jay Kreps commented on KAFKA-1710: -- The reason I ask is because the per-partition lock is

[jira] [Commented] (KAFKA-1710) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183775#comment-14183775 ] Jay Kreps commented on KAFKA-1710: -- You could try some profiling and see if you see any

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183787#comment-14183787 ] Jay Kreps commented on KAFKA-1501: -- Oh, man, my heart is broken, I was sure that was

[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-tabpanelfocusedCommentId=14181569#comment-14181569 ] Jay Kreps commented on KAFKA-1683: -- I had imagined the auth happening in the network

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181795#comment-14181795 ] Jay Kreps commented on KAFKA-1501: -- Nice! transient unit tests failures due to port

[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-tabpanelfocusedCommentId=14182024#comment-14182024 ] Jay Kreps commented on KAFKA-1683: -- Here is what I was imagining, not sure if this is

[jira] [Commented] (KAFKA-1710) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14182219#comment-14182219 ] Jay Kreps commented on KAFKA-1710: -- Well so we need to do a very quick lock around the

[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-tabpanelfocusedCommentId=14179081#comment-14179081 ] Jay Kreps commented on KAFKA-1477: -- I took a look at this patch in a little more detail,

[jira] [Commented] (KAFKA-1710) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175551#comment-14175551 ] Jay Kreps commented on KAFKA-1710: -- [~Bmis13] What is the performance you see? What do

[jira] [Commented] (KAFKA-1710) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175586#comment-14175586 ] Jay Kreps commented on KAFKA-1710: -- Well but of course you can't have multiple threads

[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-tabpanelfocusedCommentId=14169717#comment-14169717 ] Jay Kreps commented on KAFKA-1646: -- Hey [~xueqiang] what is the latency impact for that

[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-tabpanelfocusedCommentId=14167057#comment-14167057 ] Jay Kreps commented on KAFKA-1555: -- w00t! provide strong consistency with reasonable

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165431#comment-14165431 ] Jay Kreps commented on KAFKA-1499: -- Agreed: UNCOMPRESSED is better. Broker-side

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

Jay Kreps created KAFKA-1695: Summary: Authenticate connection to Zookeeper Key: KAFKA-1695 URL: https://issues.apache.org/jira/browse/KAFKA-1695 Project: Kafka Issue Type: Sub-task

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

Jay Kreps created KAFKA-1696: Summary: Kafka should be able to generate Hadoop delegation tokens Key: KAFKA-1696 URL: https://issues.apache.org/jira/browse/KAFKA-1696 Project: Kafka Issue Type:

[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-tabpanelfocusedCommentId=14164557#comment-14164557 ] Jay Kreps commented on KAFKA-1646: -- Interesting. What is the behavior of

[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-tabpanelfocusedCommentId=14162106#comment-14162106 ] Jay Kreps commented on KAFKA-1646: -- Ah, you are saying Windows does a worse job of

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

[ https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162106#comment-14162106 ] Jay Kreps edited comment on KAFKA-1646 at 10/7/14 6:23 PM: --- Ah,

[jira] [Created] (KAFKA-1682) Security for Kafka

Jay Kreps created KAFKA-1682: Summary: Security for Kafka Key: KAFKA-1682 URL: https://issues.apache.org/jira/browse/KAFKA-1682 Project: Kafka Issue Type: New Feature Affects Versions: 0.9.0

[jira] [Updated] (KAFKA-1682) Security for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1682: - Description: Parent ticket for security. Wiki and discussion is here:

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

Jay Kreps created KAFKA-1683: Summary: Implement a session concept in the socket server Key: KAFKA-1683 URL: https://issues.apache.org/jira/browse/KAFKA-1683 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-1684) Implement SSL authentication

Jay Kreps created KAFKA-1684: Summary: Implement SSL authentication Key: KAFKA-1684 URL: https://issues.apache.org/jira/browse/KAFKA-1684 Project: Kafka Issue Type: Sub-task Affects

[jira] [Updated] (KAFKA-1684) Implement TLS/SSL authentication

[ https://issues.apache.org/jira/browse/KAFKA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1684: - Summary: Implement TLS/SSL authentication (was: Implement SSL authentication) Implement TLS/SSL

[jira] [Created] (KAFKA-1685) Implement TLS/SSL tests

Jay Kreps created KAFKA-1685: Summary: Implement TLS/SSL tests Key: KAFKA-1685 URL: https://issues.apache.org/jira/browse/KAFKA-1685 Project: Kafka Issue Type: Sub-task Affects Versions:

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

Jay Kreps created KAFKA-1686: Summary: Implement SASL/Kerberos Key: KAFKA-1686 URL: https://issues.apache.org/jira/browse/KAFKA-1686 Project: Kafka Issue Type: Sub-task Affects Versions:

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

Jay Kreps created KAFKA-1687: Summary: SASL tests Key: KAFKA-1687 URL: https://issues.apache.org/jira/browse/KAFKA-1687 Project: Kafka Issue Type: Sub-task Reporter: Jay Kreps We

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

Jay Kreps created KAFKA-1688: Summary: Add authorization interface and naive implementation Key: KAFKA-1688 URL: https://issues.apache.org/jira/browse/KAFKA-1688 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-1684) Implement TLS/SSL authentication

[ https://issues.apache.org/jira/browse/KAFKA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162839#comment-14162839 ] Jay Kreps commented on KAFKA-1684: -- We may be able to get most of the implementation for

[jira] [Updated] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1430: - Priority: Blocker (was: Major) Purgatory redesign -- Key: KAFKA-1430

[jira] [Reopened] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps reopened KAFKA-1430: -- This change reverted KAFKA-1468. That was the issue where we had huge pauses due to using remove() on

[jira] [Commented] (KAFKA-1430) Purgatory redesign

[ https://issues.apache.org/jira/browse/KAFKA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160513#comment-14160513 ] Jay Kreps commented on KAFKA-1430: -- Yes it was committed. Purgatory redesign

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160789#comment-14160789 ] Jay Kreps commented on KAFKA-1305: -- FWIW, from my perspective being able to enable auto

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160828#comment-14160828 ] Jay Kreps commented on KAFKA-1305: -- Well I guess the point is that they shouldn't be

[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-tabpanelfocusedCommentId=14161185#comment-14161185 ] Jay Kreps commented on KAFKA-1670: -- Actually the reason for limiting the segments to 4GB

[jira] [Commented] (KAFKA-1677) Governor on concurrent replica reassignments

[ https://issues.apache.org/jira/browse/KAFKA-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161188#comment-14161188 ] Jay Kreps commented on KAFKA-1677: -- Agreed, LinkedIn is doing a similar thing. This

[jira] [Updated] (KAFKA-1668) TopicCommand doesn't warn if --topic argument doesn't match any topics

[ https://issues.apache.org/jira/browse/KAFKA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1668: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed, thanks. TopicCommand

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158331#comment-14158331 ] Jay Kreps commented on KAFKA-1499: -- Hey [~jjkoshy] I agree that you can kind of argue for

[jira] [Commented] (KAFKA-1660) Ability to call close() with a timeout on the Java Kafka Producer.

[ https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154882#comment-14154882 ] Jay Kreps commented on KAFKA-1660: -- Gotcha, so if I understand close(time) is effectively

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153407#comment-14153407 ] Jay Kreps commented on KAFKA-1499: -- Here is the problem with compaction. Currently the

[jira] [Resolved] (KAFKA-520) ConsumerIterator implemented by KafkaStream doesn't follow Java practices

[ https://issues.apache.org/jira/browse/KAFKA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-520. - Resolution: Duplicate This is being fixed in the new consumer implementation. ConsumerIterator

[jira] [Commented] (KAFKA-1659) Ability to cleanly abort the KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153999#comment-14153999 ] Jay Kreps commented on KAFKA-1659: -- This makes sense, I think what you are asking for is

[jira] [Commented] (KAFKA-1659) Ability to cleanly abort the KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154292#comment-14154292 ] Jay Kreps commented on KAFKA-1659: -- Yeah that makes sense. I feel like maybe the real

[jira] [Commented] (KAFKA-1659) Ability to cleanly abort the KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154322#comment-14154322 ] Jay Kreps commented on KAFKA-1659: -- Yeah and that is in some sense a bigger problem

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154336#comment-14154336 ] Jay Kreps commented on KAFKA-1499: -- Yeah I totally agree. I agree that some heuristic

[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-tabpanelfocusedCommentId=14151788#comment-14151788 ] Jay Kreps commented on KAFKA-1646: -- Can you describe the problem in a little more detail?

[jira] [Commented] (KAFKA-1590) Binarize trace level request logging along with debug level text logging

[ https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151785#comment-14151785 ] Jay Kreps commented on KAFKA-1590: -- Hmm, I think this is going to be a bit confusing.

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152354#comment-14152354 ] Jay Kreps commented on KAFKA-1499: -- Hey Joel, that makes sense. I chatted with Neha. I

[jira] [Commented] (KAFKA-1590) Binarize trace level request logging along with debug level text logging

[ https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151168#comment-14151168 ] Jay Kreps commented on KAFKA-1590: -- How will people read these binary files? Binarize

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151169#comment-14151169 ] Jay Kreps commented on KAFKA-1499: -- Hey [~jjkoshy] you can only specify log configs at

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

[ https://issues.apache.org/jira/browse/KAFKA-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149875#comment-14149875 ] Jay Kreps commented on KAFKA-1642: -- Yeah a sample program that reproduces the issue would

[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-tabpanelfocusedCommentId=14148371#comment-14148371 ] Jay Kreps commented on KAFKA-1555: -- This is a good discussion, I am glad we are taking

[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-tabpanelfocusedCommentId=14148483#comment-14148483 ] Jay Kreps commented on KAFKA-1555: -- 1. Yeah this may have been a mistake. I think

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

[ https://issues.apache.org/jira/browse/KAFKA-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140868#comment-14140868 ] Jay Kreps commented on KAFKA-1642: -- The intended behavior is that the client will

[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-tabpanelfocusedCommentId=14140949#comment-14140949 ] Jay Kreps commented on KAFKA-1640: -- Hmm, is there anything we can do to make the cause

[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-tabpanelfocusedCommentId=14136206#comment-14136206 ] Jay Kreps commented on KAFKA-1618: -- I think the problem with a default port is that yes,

[jira] [Commented] (KAFKA-1590) Binarize trace level request logging along with debug level text logging

[ https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131791#comment-14131791 ] Jay Kreps commented on KAFKA-1590: -- Are we saying that we would only produce a binary log

[jira] [Commented] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127702#comment-14127702 ] Jay Kreps commented on KAFKA-1627: -- Unfortunately the website has to remain on svn as

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127703#comment-14127703 ] Jay Kreps commented on KAFKA-1501: -- That's awesome, thanks for digging in on this.

[jira] [Commented] (KAFKA-1626) Use Jekyll for website

[ https://issues.apache.org/jira/browse/KAFKA-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14124518#comment-14124518 ] Jay Kreps commented on KAFKA-1626: -- Yeah I think this makes a lot of sense. The switch

[jira] [Updated] (KAFKA-1621) Standardize --messages option in perf scripts

[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1621: - Labels: newbie (was: ) Standardize --messages option in perf scripts

[jira] [Updated] (KAFKA-1621) Standardize --messages option in perf scripts

[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1621: - Affects Version/s: 0.8.1.1 Standardize --messages option in perf scripts

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14115685#comment-14115685 ] Jay Kreps commented on KAFKA-1554: -- And just to confirm this is after a clean shutdown?

[jira] [Commented] (KAFKA-656) Add Quotas to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110789#comment-14110789 ] Jay Kreps commented on KAFKA-656: - Hey [~ab10anand], that is right--in general for a fire

[jira] [Commented] (KAFKA-656) Add Quotas to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111339#comment-14111339 ] Jay Kreps commented on KAFKA-656: - Another alternative which might make thing simpler would

[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-tabpanelfocusedCommentId=14107844#comment-14107844 ] Jay Kreps commented on KAFKA-1489: -- I agree I think generally it makes most sense to

[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-tabpanelfocusedCommentId=14107867#comment-14107867 ] Jay Kreps commented on KAFKA-1489: -- Max utilization percent would be ideal but Java

[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-tabpanelfocusedCommentId=14106431#comment-14106431 ] Jay Kreps commented on KAFKA-1489: -- Yeah I get what you want here, I think you basically

[jira] [Commented] (KAFKA-656) Add Quotas to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100840#comment-14100840 ] Jay Kreps commented on KAFKA-656: - Hey [~ab10anand] a couple of suggestions: 1. You could

[jira] [Comment Edited] (KAFKA-656) Add Quotas to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100840#comment-14100840 ] Jay Kreps edited comment on KAFKA-656 at 8/18/14 4:51 PM: -- Hey

[jira] [Updated] (KAFKA-1576) Make deleteTopic a bit more user friendly

[ https://issues.apache.org/jira/browse/KAFKA-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1576: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch! Committed to

[jira] [Commented] (KAFKA-656) Add Quotas to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094589#comment-14094589 ] Jay Kreps commented on KAFKA-656: - Hey [~ab10anand], I would rather not do explicit leases.

[jira] [Commented] (KAFKA-1586) support sticky partitioning in the new producer

[ https://issues.apache.org/jira/browse/KAFKA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093185#comment-14093185 ] Jay Kreps commented on KAFKA-1586: -- We made partitioning pluggable so you could plug in

[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-tabpanelfocusedCommentId=14086984#comment-14086984 ] Jay Kreps commented on KAFKA-1555: -- Hey [~gwenshap], to answer your question, the

[jira] [Updated] (KAFKA-1566) Kafka environment configuration (kafka-env.sh)

[ https://issues.apache.org/jira/browse/KAFKA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1566: - Labels: newbie (was: ) Kafka environment configuration (kafka-env.sh)

[jira] [Commented] (KAFKA-1566) Kafka environment configuration (kafka-env.sh)

[ https://issues.apache.org/jira/browse/KAFKA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14083724#comment-14083724 ] Jay Kreps commented on KAFKA-1566: -- That makes sense. How do you find the env.sh script?

[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-tabpanelfocusedCommentId=14083075#comment-14083075 ] Jay Kreps commented on KAFKA-1555: -- I think we may be confusing a few things: 1. The

[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-tabpanelfocusedCommentId=14081912#comment-14081912 ] Jay Kreps commented on KAFKA-1489: -- Thinking about this I think the right way for this to

[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-tabpanelfocusedCommentId=14079483#comment-14079483 ] Jay Kreps commented on KAFKA-1507: -- Maybe the best plan would be to retain the option we

[jira] [Commented] (KAFKA-865) Mavenize and separate the client.

[ https://issues.apache.org/jira/browse/KAFKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078121#comment-14078121 ] Jay Kreps commented on KAFKA-865: - The new producer has been completed and the consumer is

[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-tabpanelfocusedCommentId=14078438#comment-14078438 ] Jay Kreps commented on KAFKA-1477: -- Yeah Hey Joe, that is a great offer. I don't

[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-tabpanelfocusedCommentId=14077182#comment-14077182 ] Jay Kreps commented on KAFKA-1507: -- I kind of feel this is not the right fix. I think

[jira] [Resolved] (KAFKA-1150) Fetch on a replicated topic does not return as soon as possible

[ https://issues.apache.org/jira/browse/KAFKA-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1150. -- Resolution: Duplicate Fetch on a replicated topic does not return as soon as possible

[jira] [Resolved] (KAFKA-1544) LogCleaner may take a long time to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1544. -- Resolution: Fixed Fix Version/s: 0.8.2 Committed, thanks! LogCleaner may take a long time to

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070542#comment-14070542 ] Jay Kreps commented on KAFKA-1414: -- Cool, that is a great speed-up either way. I'm fine

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068561#comment-14068561 ] Jay Kreps commented on KAFKA-1414: -- [~arhagnel] I share your concern. I just want to make

[jira] [Commented] (KAFKA-1546) Automate replica lag tuning

[ https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068575#comment-14068575 ] Jay Kreps commented on KAFKA-1546: -- I think I was being a little vague. What I was trying

[jira] [Comment Edited] (KAFKA-1546) Automate replica lag tuning

[ https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068575#comment-14068575 ] Jay Kreps edited comment on KAFKA-1546 at 7/21/14 2:41 PM: --- I

[jira] [Updated] (KAFKA-1539) Due to OS caching Kafka might loose offset files which causes full reset of data

[ https://issues.apache.org/jira/browse/KAFKA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1539: - Attachment: KAFKA-1539.patch Due to OS caching Kafka might loose offset files which causes full reset

[jira] [Commented] (KAFKA-1539) Due to OS caching Kafka might loose offset files which causes full reset of data

[ https://issues.apache.org/jira/browse/KAFKA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068831#comment-14068831 ] Jay Kreps commented on KAFKA-1539: -- Created reviewboard

[jira] [Commented] (KAFKA-1539) Due to OS caching Kafka might loose offset files which causes full reset of data

[ https://issues.apache.org/jira/browse/KAFKA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068837#comment-14068837 ] Jay Kreps commented on KAFKA-1539: -- This is a really good catch, were clearly thinking

[jira] [Commented] (KAFKA-1553) TopicMetadataResponse.brokers not read in scala producer?

[ https://issues.apache.org/jira/browse/KAFKA-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069141#comment-14069141 ] Jay Kreps commented on KAFKA-1553: -- We have been working on rewriting the clients. We

[jira] [Resolved] (KAFKA-322) Remove one-off Send objects

[ https://issues.apache.org/jira/browse/KAFKA-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-322. - Resolution: Fixed This was fixed a long while back, cleaning up. Remove one-off Send objects

[jira] [Updated] (KAFKA-1330) Implement subscribe(TopicPartition...partitions) in the new consumer

[ https://issues.apache.org/jira/browse/KAFKA-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1330: - Attachment: KAFKA-1330_2014-07-21_16:44:23.patch Implement subscribe(TopicPartition...partitions) in

[jira] [Commented] (KAFKA-1330) Implement subscribe(TopicPartition...partitions) in the new consumer

[ https://issues.apache.org/jira/browse/KAFKA-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069525#comment-14069525 ] Jay Kreps commented on KAFKA-1330: -- Updated reviewboard

[jira] [Resolved] (KAFKA-1539) Due to OS caching Kafka might loose offset files which causes full reset of data

[ https://issues.apache.org/jira/browse/KAFKA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1539. -- Resolution: Fixed I'm checking this in since it seems to fix a clear problem, but [~arhagnel] it

<    1   2   3   4   5   6   7   8   9   10   >