[jira] [Created] (KAFKA-3790) Default options when removing ACLs do not comply with documentation

2016-06-03 Thread JIRA
Sébastien Launay created KAFKA-3790: --- Summary: Default options when removing ACLs do not comply with documentation Key: KAFKA-3790 URL: https://issues.apache.org/jira/browse/KAFKA-3790 Project

[jira] [Created] (KAFKA-3840) OS auto tuning for socket buffer size in clients not allowed through configuration

2016-06-14 Thread JIRA
Sébastien Launay created KAFKA-3840: --- Summary: OS auto tuning for socket buffer size in clients not allowed through configuration Key: KAFKA-3840 URL: https://issues.apache.org/jira/browse/KAFKA-3840

[jira] [Created] (KAFKA-3948) Invalid broker port in Zookeeper when SSL is enabled

2016-07-11 Thread JIRA
Gérald Quintana created KAFKA-3948: -- Summary: Invalid broker port in Zookeeper when SSL is enabled Key: KAFKA-3948 URL: https://issues.apache.org/jira/browse/KAFKA-3948 Project: Kafka Issue

[jira] [Updated] (KAFKA-3948) Invalid broker port in Zookeeper when SSL is enabled

2016-07-11 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gérald Quintana updated KAFKA-3948: --- Description: {code} listeners=SSL://:9093,PLAINTEXT://:9092 port=9093 {code} gives in

[jira] [Updated] (KAFKA-3948) Invalid broker port in Zookeeper when SSL is enabled

2016-07-11 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gérald Quintana updated KAFKA-3948: --- Description: With broker config {code} listeners=SSL://:9093,PLAINTEXT://:9092 port=9093

[jira] [Created] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

2016-07-20 Thread JIRA
Juho Mäkinen created KAFKA-3978: --- Summary: Cannot truncate to a negative offset (-1) exception at broker startup Key: KAFKA-3978 URL: https://issues.apache.org/jira/browse/KAFKA-3978 Project: Kafka

[jira] [Updated] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

2016-07-20 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juho Mäkinen updated KAFKA-3978: Description: During broker startup sequence the broker server.log has this exception. Problem

[jira] [Updated] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

2016-07-20 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juho Mäkinen updated KAFKA-3978: Description: During broker startup sequence the broker server.log has this exception. Problem

[jira] [Created] (KAFKA-4022) TopicCommand is using default max.message.bytes instead of broker's setting

2016-08-05 Thread JIRA
Tomasz Trębski created KAFKA-4022: - Summary: TopicCommand is using default max.message.bytes instead of broker's setting Key: KAFKA-4022 URL: https://issues.apache.org/jira/browse/KAFKA-4022 Pr

[jira] [Commented] (KAFKA-4022) TopicCommand is using default max.message.bytes instead of broker's setting

2016-08-05 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409207#comment-15409207 ] Tomasz Trębski commented on KAFKA-4022: --- Hi, First time that I report anyt

[jira] [Comment Edited] (KAFKA-4022) TopicCommand is using default max.message.bytes instead of broker's setting

2016-08-05 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409207#comment-15409207 ] Tomasz Trębski edited comment on KAFKA-4022 at 8/5/16 9:3

[jira] [Commented] (KAFKA-4022) TopicCommand is using default max.message.bytes instead of broker's setting

2016-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413088#comment-15413088 ] Tomasz Trębski commented on KAFKA-4022: --- [~vahid] , so maybe I was misguided by

[jira] [Commented] (KAFKA-4022) TopicCommand is using default max.message.bytes instead of broker's setting

2016-08-09 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414281#comment-15414281 ] Tomasz Trębski commented on KAFKA-4022: --- Yes, that generally my concern here

[jira] [Commented] (KAFKA-2122) Remove controller.message.queue.size Config

2015-04-20 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502583#comment-14502583 ] 王博 commented on KAFKA-2122: --- Which version this patch is based on? I found KAFKA-2122_201

[jira] [Created] (KAFKA-2159) offsets.topic.segment.bytes and offsets.topic.retention.minutes are ignored

2015-04-30 Thread - (JIRA)
- created KAFKA-2159: Summary: offsets.topic.segment.bytes and offsets.topic.retention.minutes are ignored Key: KAFKA-2159 URL: https://issues.apache.org/jira/browse/KAFKA-2159 Project: Kafka Issue

[jira] [Commented] (KAFKA-2159) offsets.topic.segment.bytes and offsets.topic.retention.minutes are ignored

2015-04-30 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521518#comment-14521518 ] Rafał Boniecki commented on KAFKA-2159: --- Possible rea

[jira] [Created] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-07 Thread JIRA
Igor Maravić created KAFKA-2176: --- Summary: DefaultPartitioner doesn't perform consistent hashing based on Key: KAFKA-2176 URL: https://issues.apache.org/jira/browse/KAFKA-2176 Project:

[jira] [Updated] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić updated KAFKA-2176: Status: Open (was: Patch Available) > DefaultPartitioner doesn't perform consistent hashi

[jira] [Updated] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić updated KAFKA-2176: Status: Patch Available (was: Open) > DefaultPartitioner doesn't perform consistent hashi

[jira] [Commented] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532514#comment-14532514 ] Igor Maravić commented on KAFKA-2176: - Created reviewboard https://reviews.apache

[jira] [Updated] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić updated KAFKA-2176: Attachment: KAFKA-2176.patch > DefaultPartitioner doesn't perform consistent hashing

[jira] [Updated] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić updated KAFKA-2176: Status: Patch Available (was: Open) > DefaultPartitioner doesn't perform consistent hashi

[jira] [Commented] (KAFKA-2169) Upgrade to zkclient-0.5

2015-05-08 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534743#comment-14534743 ] Igor Maravić commented on KAFKA-2169: - We, Spotify, have just been hit by a

[jira] [Commented] (KAFKA-2169) Upgrade to zkclient-0.5

2015-05-09 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536281#comment-14536281 ] Igor Maravić commented on KAFKA-2169: - [~parth.brahmbhatt] If you look at the s

[jira] [Created] (KAFKA-2182) zkClient dies if there is any exception while reconnecting

2015-05-09 Thread JIRA
Igor Maravić created KAFKA-2182: --- Summary: zkClient dies if there is any exception while reconnecting Key: KAFKA-2182 URL: https://issues.apache.org/jira/browse/KAFKA-2182 Project: Kafka Issue

[jira] [Commented] (KAFKA-2182) zkClient dies if there is any exception while reconnecting

2015-05-09 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536286#comment-14536286 ] Igor Maravić commented on KAFKA-2182: - This is continuation of discussion from K

[jira] [Commented] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-11 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539393#comment-14539393 ] Igor Maravić commented on KAFKA-2176: - I don't see why this wouldn't be

[jira] [Commented] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539430#comment-14539430 ] Igor Maravić commented on KAFKA-2176: - Didn't know that. How much is th

[jira] [Commented] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539429#comment-14539429 ] Igor Maravić commented on KAFKA-2176: - Didn't know that. How much is th

[jira] [Issue Comment Deleted] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić updated KAFKA-2176: Comment: was deleted (was: Didn't know that. How much is this battle tested? We had a l

[jira] [Commented] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-13 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541484#comment-14541484 ] Igor Maravić commented on KAFKA-2176: - Partitioning is working as expected with

[jira] [Resolved] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-13 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić resolved KAFKA-2176. - Resolution: Won't Fix > DefaultPartitioner doesn't perform consistent has

[jira] [Updated] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

2015-05-13 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Maravić updated KAFKA-2176: Status: Open (was: Patch Available) > DefaultPartitioner doesn't perform consistent hashi

[jira] [Created] (KAFKA-2202) ConsumerPerformance reports a throughput much higher than the actual one

2015-05-19 Thread JIRA
Micael Capitão created KAFKA-2202: - Summary: ConsumerPerformance reports a throughput much higher than the actual one Key: KAFKA-2202 URL: https://issues.apache.org/jira/browse/KAFKA-2202 Project

[jira] [Updated] (KAFKA-2202) ConsumerPerformance reports a throughput much higher than the actual one

2015-05-19 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Micael Capitão updated KAFKA-2202: -- Description: I've been using the kafka.tools.ConsumerPerformance tool for some benchma

[jira] [Created] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

2016-11-03 Thread JIRA
Stig Rohde Døssing created KAFKA-4375: - Summary: Kafka consumer may swallow some interrupts meant for the calling thread Key: KAFKA-4375 URL: https://issues.apache.org/jira/browse/KAFKA-4375

[jira] [Commented] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

2016-11-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634337#comment-15634337 ] Stig Rohde Døssing commented on KAFKA-4375: --- Happy to hear that. I&#x

[jira] [Assigned] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

2016-11-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing reassigned KAFKA-4375: - Assignee: Stig Rohde Døssing > Kafka consumer may swallow some interrupts me

[jira] [Updated] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

2016-11-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated KAFKA-4375: -- Affects Version/s: 0.10.1.0 Status: Patch Available (was: Open) Reset

[jira] [Issue Comment Deleted] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

2016-11-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated KAFKA-4375: -- Comment: was deleted (was: Reset thread interrupt state in a few places where

[jira] [Created] (KAFKA-4387) KafkaConsumer will enter an infinite loop if the polling thread is interrupted, and either commitSync or committed is called

2016-11-07 Thread JIRA
://issues.apache.org/jira/browse/KAFKA-4387 Project: Kafka Issue Type: Bug Components: clients Affects Versions: 0.10.0.1 Reporter: Stig Rohde Døssing Assignee: Stig Rohde Døssing When the KafkaConsumer.commitSync method is called, the

[jira] [Commented] (KAFKA-4387) KafkaConsumer will enter an infinite loop if the polling thread is interrupted, and either commitSync or committed is called

2016-11-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644936#comment-15644936 ] Stig Rohde Døssing commented on KAFKA-4387: --- Fine by me. I'll make a

[jira] [Updated] (KAFKA-4387) KafkaConsumer will enter an infinite loop if the polling thread is interrupted, and either commitSync or committed is called

2016-11-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated KAFKA-4387: -- Status: Patch Available (was: Open) > KafkaConsumer will enter an infinite loop if

[jira] [Comment Edited] (KAFKA-1894) Avoid long or infinite blocking in the consumer

2016-11-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654191#comment-15654191 ] Stig Rohde Døssing edited comment on KAFKA-1894 at 11/10/16 2:3

[jira] [Commented] (KAFKA-1894) Avoid long or infinite blocking in the consumer

2016-11-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654191#comment-15654191 ] Stig Rohde Døssing commented on KAFKA-1894: --- Suggestion for a fix for

[jira] [Created] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

2016-11-28 Thread JIRA
Xavier Léauté created KAFKA-4458: Summary: Add per partition metrics for in-sync and assigned replica count Key: KAFKA-4458 URL: https://issues.apache.org/jira/browse/KAFKA-4458 Project: Kafka

[jira] [Commented] (KAFKA-4436) Provide builder pattern for StreamsConfig

2016-11-28 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703682#comment-15703682 ] Xavier Léauté commented on KAFKA-4436: -- [~gwenshap] One of the difference I

[jira] [Assigned] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

2016-11-29 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-4458: Assignee: Xavier Léauté > Add per partition metrics for in-sync and assigned replica co

[jira] [Commented] (KAFKA-3834) Consumer should not block in poll on coordinator discovery

2016-11-30 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710240#comment-15710240 ] Sönke Liebau commented on KAFKA-3834: - Does anybody know whether this is b

[jira] [Created] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
Sinóros-Szabó Péter created KAFKA-4478: -- Summary: Deadlock between heartbeat executor, group metadata manager and request handler Key: KAFKA-4478 URL: https://issues.apache.org/jira/browse/KAFKA-4478

[jira] [Updated] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sinóros-Szabó Péter updated KAFKA-4478: --- Affects Version/s: 0.10.1.0 > Deadlock between heartbeat executor, group metad

[jira] [Updated] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sinóros-Szabó Péter updated KAFKA-4478: --- Labels: reliability (was: ) > Deadlock between heartbeat executor, group metad

[jira] [Updated] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sinóros-Szabó Péter updated KAFKA-4478: --- Attachment: kafka-1.state-change.log kafka-1.server.log.2016-12-01-21

[jira] [Updated] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sinóros-Szabó Péter updated KAFKA-4478: --- Description: We are running a 0.10.1.0 cluster with 3 brokers with ids 0, 1 and 2. At

[jira] [Updated] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sinóros-Szabó Péter updated KAFKA-4478: --- Description: We are running a 0.10.1.0 cluster with 3 brokers with ids 0, 1 and 2. At

[jira] [Commented] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715094#comment-15715094 ] Sinóros-Szabó Péter commented on KAFKA-4478: Yes, locked threads and s

[jira] [Created] (KAFKA-4481) Relax Kafka Streams API type constraints

2016-12-02 Thread JIRA
Xavier Léauté created KAFKA-4481: Summary: Relax Kafka Streams API type constraints Key: KAFKA-4481 URL: https://issues.apache.org/jira/browse/KAFKA-4481 Project: Kafka Issue Type

[jira] [Commented] (KAFKA-4481) Relax Kafka Streams API type constraints

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716140#comment-15716140 ] Xavier Léauté commented on KAFKA-4481: -- This change should be backwards-compat

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4481: - Description: Streams API methods that apply transformations to streams are currently invariant

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4481: - Issue Type: Bug (was: Improvement) > Relax Kafka Streams API type constrai

[jira] [Work started] (KAFKA-4481) Relax Kafka Streams API type constraints

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4481 started by Xavier Léauté. > Relax Kafka Streams API type constrai

[jira] [Work started] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4458 started by Xavier Léauté. > Add per partition metrics for in-sync and assigned replica co

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4481: - Status: Patch Available (was: In Progress) > Relax Kafka Streams API type constrai

[jira] [Updated] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

2016-12-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4458: - Status: Patch Available (was: In Progress) > Add per partition metrics for in-sync and assig

[jira] [Created] (KAFKA-4491) OOME when Java client can not connect to brokers

2016-12-06 Thread JIRA
Gérald Quintana created KAFKA-4491: -- Summary: OOME when Java client can not connect to brokers Key: KAFKA-4491 URL: https://issues.apache.org/jira/browse/KAFKA-4491 Project: Kafka Issue

[jira] [Commented] (KAFKA-4493) Connections to Kafka brokers should be validated

2016-12-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725713#comment-15725713 ] Gérald Quintana commented on KAFKA-4493: See also KAFKA-4491 > Connect

[jira] [Commented] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743832#comment-15743832 ] Michał Woś commented on KAFKA-1407: --- [~dmitrybugaychenko] +1 The same issue in 0.8

[jira] [Issue Comment Deleted] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michał Woś updated KAFKA-1407: -- Comment: was deleted (was: [~dmitrybugaychenko] +1 The same issue in 0.8.2.0. Scenario 1. Broker looses

[jira] [Comment Edited] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743832#comment-15743832 ] Michał Woś edited comment on KAFKA-1407 at 12/13/16 2:0

[jira] [Commented] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743840#comment-15743840 ] Michał Woś commented on KAFKA-1407: --- [~dmitrybugaychenko] +1 The same issue in 0.8

[jira] [Comment Edited] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743840#comment-15743840 ] Michał Woś edited comment on KAFKA-1407 at 12/13/16 2:0

[jira] [Comment Edited] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743840#comment-15743840 ] Michał Woś edited comment on KAFKA-1407 at 12/13/16 2:0

[jira] [Comment Edited] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743840#comment-15743840 ] Michał Woś edited comment on KAFKA-1407 at 12/13/16 2:2

[jira] [Comment Edited] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743840#comment-15743840 ] Michał Woś edited comment on KAFKA-1407 at 12/13/16 2:2

[jira] [Comment Edited] (KAFKA-1407) Broker can not return to ISR because of BadVersionException

2016-12-12 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743840#comment-15743840 ] Michał Woś edited comment on KAFKA-1407 at 12/13/16 2:2

[jira] [Created] (KAFKA-4567) Connect Producer and Consumer ignore ssl parameters configured for worker

2016-12-22 Thread JIRA
Sönke Liebau created KAFKA-4567: --- Summary: Connect Producer and Consumer ignore ssl parameters configured for worker Key: KAFKA-4567 URL: https://issues.apache.org/jira/browse/KAFKA-4567 Project: Kafka

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

2017-01-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795530#comment-15795530 ] Gérald Quintana commented on KAFKA-2394: It would be great to be able to mix

[jira] [Commented] (KAFKA-1368) Upgrade log4j

2017-01-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796263#comment-15796263 ] Gérald Quintana commented on KAFKA-1368: It would be great to be able to mix

[jira] [Created] (KAFKA-4846) Use KafkaProducer without allocating a new ProducerRecord for each message sent

2017-03-06 Thread JIRA
Mikael Ståldal created KAFKA-4846: - Summary: Use KafkaProducer without allocating a new ProducerRecord for each message sent Key: KAFKA-4846 URL: https://issues.apache.org/jira/browse/KAFKA-4846

[jira] [Updated] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

2017-03-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4856: - Description: Calling KafkaProducer.close() from multiple threads simultaneously may cause the

[jira] [Created] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

2017-03-06 Thread JIRA
Xavier Léauté created KAFKA-4856: Summary: Calling KafkaProducer.close() from multiple threads may cause spurious error Key: KAFKA-4856 URL: https://issues.apache.org/jira/browse/KAFKA-4856 Project

[jira] [Updated] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

2017-03-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4856: - Description: Calling KafkaProducer.close() from multiple threads simultaneously may cause the

[jira] [Updated] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

2017-03-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4856: - Description: Calling {{KafkaProducer.close()}} from multiple threads simultaneously may cause

[jira] [Created] (KAFKA-4860) Kafka batch files does not support path with spaces

2017-03-06 Thread JIRA
Vladimír Kleštinec created KAFKA-4860: - Summary: Kafka batch files does not support path with spaces Key: KAFKA-4860 URL: https://issues.apache.org/jira/browse/KAFKA-4860 Project: Kafka

[jira] [Updated] (KAFKA-4860) Kafka batch files does not support path with spaces

2017-03-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimír Kleštinec updated KAFKA-4860: -- Status: Patch Available (was: Open) > Kafka batch files does not support path w

[jira] [Created] (KAFKA-4863) Querying window store may return unwanted keys

2017-03-07 Thread JIRA
Xavier Léauté created KAFKA-4863: Summary: Querying window store may return unwanted keys Key: KAFKA-4863 URL: https://issues.apache.org/jira/browse/KAFKA-4863 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4863) Querying window store may return unwanted keys

2017-03-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4863: - Description: Using variable length keys in a window store may cause unwanted results to be

[jira] [Updated] (KAFKA-4863) Querying window store may return unwanted keys

2017-03-07 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4863: - Affects Version/s: 0.10.2.0 > Querying window store may return unwanted k

[jira] [Created] (KAFKA-4876) WindowStore.fetch(key, 0, Long.MaxValue) is very slow

2017-03-09 Thread JIRA
Xavier Léauté created KAFKA-4876: Summary: WindowStore.fetch(key, 0, Long.MaxValue) is very slow Key: KAFKA-4876 URL: https://issues.apache.org/jira/browse/KAFKA-4876 Project: Kafka Issue

[jira] [Updated] (KAFKA-4883) invalid client sasl.jaas.config triggers NullPointerException

2017-03-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4883: - Priority: Minor (was: Major) > invalid client sasl.jaas.config triggers NullPointerExcept

[jira] [Created] (KAFKA-4883) invalid client sasl.jaas.config triggers NullPointerException

2017-03-10 Thread JIRA
Xavier Léauté created KAFKA-4883: Summary: invalid client sasl.jaas.config triggers NullPointerException Key: KAFKA-4883 URL: https://issues.apache.org/jira/browse/KAFKA-4883 Project: Kafka

[jira] [Commented] (KAFKA-4829) Improve logging of StreamTask commits

2017-03-13 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907078#comment-15907078 ] Nicolas Fouché commented on KAFKA-4829: --- Some comments on how we felt that

[jira] [Created] (KAFKA-4913) creating a window store with one segment throws division by zero error

2017-03-16 Thread JIRA
Xavier Léauté created KAFKA-4913: Summary: creating a window store with one segment throws division by zero error Key: KAFKA-4913 URL: https://issues.apache.org/jira/browse/KAFKA-4913 Project: Kafka

[jira] [Commented] (KAFKA-4863) Querying window store may return unwanted keys

2017-03-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928902#comment-15928902 ] Xavier Léauté commented on KAFKA-4863: -- The current patch appears to solve

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

2017-03-22 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937220#comment-15937220 ] Sönke Liebau commented on KAFKA-4930: - I've created a potential fix for t

[jira] [Created] (KAFKA-4938) Creating a connector with missing name parameter throws a NullPointerException

2017-03-22 Thread JIRA
Sönke Liebau created KAFKA-4938: --- Summary: Creating a connector with missing name parameter throws a NullPointerException Key: KAFKA-4938 URL: https://issues.apache.org/jira/browse/KAFKA-4938 Project

[jira] [Created] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

2017-03-23 Thread JIRA
Johan Ström created KAFKA-4943: -- Summary: SCRAM secret's should be better protected with Zookeeper ACLs Key: KAFKA-4943 URL: https://issues.apache.org/jira/browse/KAFKA-4943 Project:

[jira] [Commented] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

2017-03-23 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937993#comment-15937993 ] Johan Ström commented on KAFKA-4943: Seems the no-acl-set-at-all was fixe

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

2017-03-23 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938458#comment-15938458 ] Sönke Liebau commented on KAFKA-4930: - After a good nights sleep I am beginnin

[jira] [Commented] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

2017-03-23 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939888#comment-15939888 ] Johan Ström commented on KAFKA-4943: I agree, it won't be totally secure unl

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