Re: Agenda item for next KIP meeting

Hey Ismael, I probably replied too late, but is it possible to add KIP-79 to the agenda as well? Jiangjie (Becket) Qin On Fri, Sep 9, 2016 at 9:57 AM, radai wrote: > Hi, > > I'd like to discuss KIP-72. could you please add me? > > On Fri, Sep 9, 2016 at 7:48 AM,

Re: [DISCUSS] Kafka 0.10.1.0 Release Plan

Hi All, I've added the release plan to the wiki: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. I've begun moving some JIRAs to 0.10.2 which didn't seem to be being actively worked on, but there's still a lot of pruning to do. If there are no objections, I will begin a

[jira] [Updated] (KAFKA-3590) KafkaConsumer fails with "Messages are rejected since there are fewer in-sync replicas than required." when polling

[ https://issues.apache.org/jira/browse/KAFKA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3590: --- Fix Version/s: 0.10.1.0 > KafkaConsumer fails with "Messages are rejected since there are

[jira] [Updated] (KAFKA-3073) KafkaConnect should support regular expression for topics

[ https://issues.apache.org/jira/browse/KAFKA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3073: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > KafkaConnect should support

[jira] [Commented] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486116#comment-15486116 ] ASF GitHub Bot commented on KAFKA-2311: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2311: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Consumer's

[GitHub] kafka pull request #1637: KAFKA-2311: Consumer's ensureNotClosed method not ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1637 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-4154) Kafka Connect fails to shutdown if it has not completed startup

[ https://issues.apache.org/jira/browse/KAFKA-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikhar Bhushan updated KAFKA-4154: --- Fix Version/s: (was: 0.10.0.2) > Kafka Connect fails to shutdown if it has not completed

[jira] [Updated] (KAFKA-740) Improve crash-safety of log segment swap

[ https://issues.apache.org/jira/browse/KAFKA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-740: -- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Improve crash-safety of log

[jira] [Updated] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3543: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Allow a variant of

[jira] [Updated] (KAFKA-4154) Kafka Connect fails to shutdown if it has not completed startup

[ https://issues.apache.org/jira/browse/KAFKA-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikhar Bhushan updated KAFKA-4154: --- Fix Version/s: (was: 0.10.1.0) 0.10.0.2 > Kafka Connect fails to

[jira] [Created] (KAFKA-4155) Remove WorkerGroupMember from Connect

Jason Gustafson created KAFKA-4155: -- Summary: Remove WorkerGroupMember from Connect Key: KAFKA-4155 URL: https://issues.apache.org/jira/browse/KAFKA-4155 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3478: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Finer Stream Flow Control >

[jira] [Updated] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2000: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Delete consumer offsets from

[jira] [Updated] (KAFKA-2045) Memory Management on the consumer

[ https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2045: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Memory Management on the

[jira] [Updated] (KAFKA-1704) Add PartitionConfig besides LogConfig

[ https://issues.apache.org/jira/browse/KAFKA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1704: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add PartitionConfig besides

[jira] [Commented] (KAFKA-2307) Drop ConsumerOffsetChecker completely

[ https://issues.apache.org/jira/browse/KAFKA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485991#comment-15485991 ] Jason Gustafson commented on KAFKA-2307: We've had the deprecation warning on this tool since

[jira] [Updated] (KAFKA-3677) Add a producer performance tuning tool

[ https://issues.apache.org/jira/browse/KAFKA-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3677: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add a producer performance

[jira] [Updated] (KAFKA-3575) Use console consumer access topic that does not exist, can not use "Control + C" to exit process

[ https://issues.apache.org/jira/browse/KAFKA-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3575: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Use console consumer access

[jira] [Updated] (KAFKA-3995) Add a new configuration "enable.comrpession.ratio.estimation" to the producer config

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3995: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add a new configuration

[jira] [Updated] (KAFKA-747) RequestChannel re-design

[ https://issues.apache.org/jira/browse/KAFKA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-747: -- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > RequestChannel re-design >

[jira] [Updated] (KAFKA-1088) Ability to create a shadow consumer group

[ https://issues.apache.org/jira/browse/KAFKA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1088: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Ability to create a shadow

[jira] [Updated] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3522: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Consider adding version

[jira] [Updated] (KAFKA-1694) KIP-4: Command line and centralized operations

[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1694: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 Description:

[jira] [Updated] (KAFKA-1206) allow Kafka to start from a resource negotiator system

[ https://issues.apache.org/jira/browse/KAFKA-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1206: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > allow Kafka to start from a

[jira] [Updated] (KAFKA-3203) Add UnknownCodecException and UnknownMagicByteException to error mapping

[ https://issues.apache.org/jira/browse/KAFKA-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3203: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add UnknownCodecException

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

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3736: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add http metrics reporter >

[jira] [Updated] (KAFKA-2787) Refactor gradle build

[ https://issues.apache.org/jira/browse/KAFKA-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2787: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Refactor gradle build >

[jira] [Updated] (KAFKA-2758) Improve Offset Commit Behavior

[ https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2758: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Improve Offset Commit

[jira] [Updated] (KAFKA-3209) Support single message transforms in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3209: --- Priority: Major (was: Critical) Fix Version/s: (was: 0.10.1.0)

[jira] [Updated] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3297: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > More optimally balanced

[jira] [Updated] (KAFKA-3596) Kafka Streams: Window expiration needs to consider more than event time

[ https://issues.apache.org/jira/browse/KAFKA-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3596: --- Affects Version/s: (was: 0.10.1.0) 0.10.0.0 Fix Version/s:

[jira] [Updated] (KAFKA-3701) Expose KafkaStreams metrics in public API

[ https://issues.apache.org/jira/browse/KAFKA-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3701: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Expose KafkaStreams metrics

[jira] [Updated] (KAFKA-2525) Update ConsumerPerformance.scala to report join group time (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2525: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Update

[jira] [Updated] (KAFKA-3714) Allow users greater access to register custom streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3714: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Allow users greater access

[jira] [Updated] (KAFKA-1776) Re-factor out existing tools that have been implemented behind the CLI

[ https://issues.apache.org/jira/browse/KAFKA-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1776: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Re-factor out existing tools

[jira] [Resolved] (KAFKA-334) Some tests fail when building on a Windows box

[ https://issues.apache.org/jira/browse/KAFKA-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-334. --- Resolution: Won't Fix Fix Version/s: (was: 0.10.1.0) Resolving this since it's been

[jira] [Resolved] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-1332. Resolution: Duplicate Assignee: Jason Gustafson Fix Version/s: (was:

[jira] [Updated] (KAFKA-4005) Add per topic compression ratio in broker and consumer.

[ https://issues.apache.org/jira/browse/KAFKA-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4005: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add per topic compression

[jira] [Commented] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485826#comment-15485826 ] Elias Levy commented on KAFKA-4153: --- Why would the other value be undefined? Default it to zero. >

[jira] [Updated] (KAFKA-1935) Consumer should use a separate socket for Coordinator connection

[ https://issues.apache.org/jira/browse/KAFKA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1935: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Consumer should use a

[jira] [Updated] (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:all-tabpanel ] Jason Gustafson updated KAFKA-3370: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add options to

[jira] [Commented] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485820#comment-15485820 ] Jason Gustafson commented on KAFKA-: I think this change probably calls for a KIP since it's a

[jira] [Updated] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Client Partitioner - Round

[jira] [Updated] (KAFKA-1617) Move Metadata Cache to TopicManager and handling of Offset Request to LogManager

[ https://issues.apache.org/jira/browse/KAFKA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1617: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Move Metadata Cache to

[jira] [Updated] (KAFKA-853) Allow OffsetFetchRequest to initialize offsets

[ https://issues.apache.org/jira/browse/KAFKA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-853: -- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Allow OffsetFetchRequest to

[jira] [Updated] (KAFKA-566) Add last modified time to the TopicMetadataRequest

[ https://issues.apache.org/jira/browse/KAFKA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-566: -- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add last modified time to the

[jira] [Updated] (KAFKA-3364) Centrallize doc generation

[ https://issues.apache.org/jira/browse/KAFKA-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3364: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Centrallize doc generation >

[jira] [Updated] (KAFKA-1895) Investigate moving deserialization and decompression out of KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1895: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Investigate moving

[jira] [Updated] (KAFKA-3366) Find a way to auto-generate expected error codes

[ https://issues.apache.org/jira/browse/KAFKA-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3366: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Find a way to auto-generate

[jira] [Commented] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485759#comment-15485759 ] Matthias J. Sax commented on KAFKA-4153: IMHO {{JoinWindows.before(100).after(50)}} would not be a

[jira] [Comment Edited] (KAFKA-2901) Extend ListGroups and DescribeGroup APIs to cover offsets

[ https://issues.apache.org/jira/browse/KAFKA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485727#comment-15485727 ] Jason Gustafson edited comment on KAFKA-2901 at 9/13/16 12:18 AM: -- We

[jira] [Resolved] (KAFKA-2901) Extend ListGroups and DescribeGroup APIs to cover offsets

[ https://issues.apache.org/jira/browse/KAFKA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-2901. Resolution: Duplicate Assignee: Jason Gustafson (was: Neha Narkhede) We changed the

[jira] [Updated] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1464: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Add a throttling option to the Kafka

[jira] [Commented] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485700#comment-15485700 ] Elias Levy commented on KAFKA-4153: --- You could do that, but it would be non-obvious to someone reading

[jira] [Created] (KAFKA-4154) Kafka Connect fails to shutdown if it has not completed startup

Shikhar Bhushan created KAFKA-4154: -- Summary: Kafka Connect fails to shutdown if it has not completed startup Key: KAFKA-4154 URL: https://issues.apache.org/jira/browse/KAFKA-4154 Project: Kafka

[jira] [Commented] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485638#comment-15485638 ] Matthias J. Sax commented on KAFKA-4153: Well, you can just call

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

Hi Jun, Yes, youre right - right now the next select() call will return immediately with the same set of keys as earlier (at least) as they were not previously handled (no memory). My assumption is that this happens under considerable load - something has to be occupying all this memory. also,

[jira] [Commented] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485561#comment-15485561 ] Elias Levy commented on KAFKA-4153: --- As a side note, the API for {{JoinWindows}} has become mangled

[jira] [Updated] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elias Levy updated KAFKA-4153: -- Flags: Patch > Incorrect KStream-KStream join behavior with asymmetric time window >

[jira] [Commented] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

[ https://issues.apache.org/jira/browse/KAFKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485524#comment-15485524 ] ASF GitHub Bot commented on KAFKA-4153: --- GitHub user eliaslevy opened a pull request:

[GitHub] kafka pull request #1846: KAFKA-4153: Fix incorrect KStream-KStream join beh...

GitHub user eliaslevy opened a pull request: https://github.com/apache/kafka/pull/1846 KAFKA-4153: Fix incorrect KStream-KStream join behavior with asymmetric time window The contribution is my original work and I license the work to the project under the project's open source

[jira] [Created] (KAFKA-4153) Incorrect KStream-KStream join behavior with asymmetric time window

Elias Levy created KAFKA-4153: - Summary: Incorrect KStream-KStream join behavior with asymmetric time window Key: KAFKA-4153 URL: https://issues.apache.org/jira/browse/KAFKA-4153 Project: Kafka

[jira] [Updated] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2063: - Assignee: Andrey Neporada (was: Alexey Ozeritskiy) > Bound fetch response size (KIP-74)

[jira] [Comment Edited] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485357#comment-15485357 ] Alexey Ozeritskiy edited comment on KAFKA-2063 at 9/12/16 9:37 PM: --- The

[jira] [Commented] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485357#comment-15485357 ] Alexey Ozeritskiy commented on KAFKA-2063: -- The approah KAFKA-3979 is better for configurations

[jira] [Assigned] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy reassigned KAFKA-2063: Assignee: Alexey Ozeritskiy (was: Andrey Neporada) > Bound fetch response size

[jira] [Updated] (KAFKA-3909) Queryable state for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3909: Assignee: Damian Guy > Queryable state for Kafka Streams > - > >

[jira] [Assigned] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4126: -- Assignee: Vahid Hashemian > No relevant log when the topic is non-existent >

Re: [VOTE] KIP-63: Unify store and downstream caching in streams

Forgot to include the stats: There were 3 binding votes (Guozhang, Neha, Gwen) and 6 non-binding votes (Matthias, Bill, Michael, Jim, Damian, Eno). Thanks to everyone that voted and participated in the discussions. Eno > On 12 Sep 2016, at 16:00, Eno Thereska wrote: >

Re: Kafka KIP meeting Sep 13 at 11:00am PST

Hi Ismael Could you please add me to the invite. rtew...@linkedin.com regards Renu On Mon, Sep 12, 2016 at 8:39 AM, Ismael Juma wrote: > Hi, Everyone, > > We plan to have a Kafka KIP meeting this coming Tuesday at 11:00am PST. If > you plan to attend but haven't received

[jira] [Created] (KAFKA-4152) Reduce severity level of metadata fetch failure logging for nonexistent topics

Andrew Olson created KAFKA-4152: --- Summary: Reduce severity level of metadata fetch failure logging for nonexistent topics Key: KAFKA-4152 URL: https://issues.apache.org/jira/browse/KAFKA-4152 Project:

[jira] [Commented] (KAFKA-4121) Allow creating broker listeners from hostname

[ https://issues.apache.org/jira/browse/KAFKA-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484524#comment-15484524 ] Joaquin Casares commented on KAFKA-4121: Thanks for the information! I ended up using this

[jira] [Resolved] (KAFKA-4121) Allow creating broker listeners from hostname

[ https://issues.apache.org/jira/browse/KAFKA-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joaquin Casares resolved KAFKA-4121. Resolution: Duplicate > Allow creating broker listeners from hostname >

Kafka KIP meeting Sep 13 at 11:00am PST

Hi, Everyone, We plan to have a Kafka KIP meeting this coming Tuesday at 11:00am PST. If you plan to attend but haven't received an invite, please let me know. The following is the tentative agenda. Agenda: KIP-54: Sticky Partition Assignment Strategy KIP-72: Allow Sizing Incoming Request Queue

[jira] [Updated] (KAFKA-4151) System tests for KIP-78

[ https://issues.apache.org/jira/browse/KAFKA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4151: --- Issue Type: New Feature (was: Bug) > System tests for KIP-78 > > >

[jira] [Created] (KAFKA-4151) System tests for KIP-78

Sumit Arrawatia created KAFKA-4151: -- Summary: System tests for KIP-78 Key: KAFKA-4151 URL: https://issues.apache.org/jira/browse/KAFKA-4151 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-63: Unify store and downstream caching in streams

KIP-63 has now been adopted, thank you! Eno > On 9 Sep 2016, at 00:21, Neha Narkhede wrote: > > +1 (binding) > > On Thu, Sep 8, 2016 at 2:34 PM Gwen Shapira wrote: > >> +1 (binding) >> >> Looks great and very detailed. Nice job, Eno :) >> >> On Thu,

[jira] [Updated] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2063: --- Assignee: Andrey Neporada > Bound fetch response size (KIP-74) > -- >

[jira] [Updated] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2063: --- Fix Version/s: 0.10.1.0 > Bound fetch response size > - > >

[jira] [Commented] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484311#comment-15484311 ] Ismael Juma commented on KAFKA-2063: PR link: https://github.com/apache/kafka/pull/1812 > Bound fetch

[jira] [Updated] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2063: --- Summary: Bound fetch response size (KIP-74) (was: Bound fetch response size) > Bound fetch response

[jira] [Updated] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2063: --- Status: Patch Available (was: Open) > Bound fetch response size (KIP-74) >

[jira] [Commented] (KAFKA-4007) Improve fetch pipelining for low values of max.poll.records

[ https://issues.apache.org/jira/browse/KAFKA-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484105#comment-15484105 ] Eno Thereska commented on KAFKA-4007: - [~hachikuji] isn't the point of max.poll.records to improve the

[GitHub] kafka pull request #1845: HOTFIX: throw exception if the Cluster object has ...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1845 HOTFIX: throw exception if the Cluster object has not been intialized in StreamMetadataState During rebalance operations the Cluster object gets set to Cluster.empty(). This can result in NPEs when

[GitHub] kafka pull request #1844: MINOR: Adjusted heartbeat and rebalancing interval...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1844 MINOR: Adjusted heartbeat and rebalancing intervals to stop triggering spuri… …ous rebalances You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-1835) Kafka new producer needs options to make blocking behavior explicit

[ https://issues.apache.org/jira/browse/KAFKA-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483605#comment-15483605 ] Bence Varga commented on KAFKA-1835: I can see two actions that can resolve this issue: A) Remove

[jira] [Created] (KAFKA-4150) Facing Message Loss When trying rolling updates

Avanish Pandey created KAFKA-4150: - Summary: Facing Message Loss When trying rolling updates Key: KAFKA-4150 URL: https://issues.apache.org/jira/browse/KAFKA-4150 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483414#comment-15483414 ] Michal Turek commented on KAFKA-3450: - Dirty workaround for this issue is to build and periodically

Build failed in Jenkins: kafka-trunk-jdk7 #1534

See Changes: [wangguoz] MINOR: catch InvalidStateStoreException in QueryableStateIntegrationTest -- [...truncated 5885 lines...] kafka.log.FileMessageSetTest > testTruncate STARTED

Re: Queryable state client read guarantees

Hi, this helps, thanks! Basically, after each read, I'll check if the key is still supposed to be on the host. Doing the check after the read is necessary to handle the case when a rebalance happens in between the metadata lookup and the store get. When checking after the read, it may happen