[jira] [Updated] (KAFKA-4948) Failure in kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGroupWithNoMembersWithNewConsumer

2017-06-05 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4948: --- Status: Patch Available (was: Open) > Failure in > kafka.admin.DescribeConsumerGroupTest.testDescrib

[jira] [Updated] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5364: --- Status: Patch Available (was: Reopened) > Producer attempts to send transactional messages before add

[jira] [Commented] (KAFKA-5378) Last Stable Offset not returned in Fetch request

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036438#comment-16036438 ] Ismael Juma commented on KAFKA-5378: Since this is a case of Kafka not complying with

[jira] [Updated] (KAFKA-5378) Last Stable Offset not returned in Fetch request

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5378: --- Priority: Critical (was: Major) > Last Stable Offset not returned in Fetch request >

[jira] [Resolved] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5355. Resolution: Fixed > Broker returns messages beyond "latest stable offset" to transactional > consum

[jira] [Comment Edited] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036327#comment-16036327 ] Ismael Juma edited comment on KAFKA-5098 at 6/4/17 4:36 PM: [~

[jira] [Updated] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5098: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > KafkaProducer.send() blocks and gener

[jira] [Reopened] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-5098: [~onurkaraman] correctly asked about the potential performance impact of doing this check for each prod

[jira] [Updated] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

2017-06-04 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5371: --- Resolution: Fixed Status: Resolved (was: Patch Available) > SyncProducerTest.testReachableSer

[jira] [Resolved] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5098. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3223 [https://github

[jira] [Updated] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4291: --- Resolution: Fixed Status: Resolved (was: Patch Available) > TopicCommand --describe shows top

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

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035902#comment-16035902 ] Ismael Juma commented on KAFKA-4913: Is this still planned for 0.11.0.0? > creating a

[jira] [Updated] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5371: --- Issue Type: Test (was: Bug) > SyncProducerTest.testReachableServer has become flaky > ---

[jira] [Updated] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5371: --- Assignee: Ismael Juma (was: Apurva Mehta) Fix Version/s: 0.11.0.0 Status: Patch Av

[jira] [Updated] (KAFKA-3096) Leader is not set to -1 when it is shutdown if followers are down

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3096: --- Fix Version/s: 0.11.1.0 > Leader is not set to -1 when it is shutdown if followers are down >

[jira] [Updated] (KAFKA-3143) inconsistent state in ZK when all replicas are dead

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3143: --- Fix Version/s: 0.11.1.0 > inconsistent state in ZK when all replicas are dead > --

[jira] [Updated] (KAFKA-3866) KerberosLogin refresh time bug and other improvements

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3866: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.0 > KerberosLogin refresh time bug and ot

[jira] [Updated] (KAFKA-3881) Remove the replacing logic from "." to "_" in Fetcher

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3881: --- Labels: newbie (was: ) > Remove the replacing logic from "." to "_" in Fetcher >

[jira] [Assigned] (KAFKA-3881) Remove the replacing logic from "." to "_" in Fetcher

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3881: -- Assignee: (was: Ismael Juma) > Remove the replacing logic from "." to "_" in Fetcher >

[jira] [Assigned] (KAFKA-4503) Expose the log dir for a partition as a metric

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4503: -- Assignee: (was: Ismael Juma) > Expose the log dir for a partition as a metric > ---

[jira] [Commented] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035884#comment-16035884 ] Ismael Juma commented on KAFKA-5031: If we don't add this validation now, we may not b

[jira] [Updated] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5031: --- Priority: Critical (was: Major) > Additional validation in validateMessagesAndAssignOffsets > ---

[jira] [Updated] (KAFKA-5214) KafkaAdminClient#apiVersions should return a public class

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5214: --- Priority: Blocker (was: Major) > KafkaAdminClient#apiVersions should return a public class >

[jira] [Updated] (KAFKA-5214) KafkaAdminClient#apiVersions should return a public class

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5214: --- Fix Version/s: 0.11.0.0 > KafkaAdminClient#apiVersions should return a public class >

[jira] [Updated] (KAFKA-5325) Connection Lose during Kafka Kerberos Renewal process

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5325: --- Status: Patch Available (was: Open) > Connection Lose during Kafka Kerberos Renewal process > ---

[jira] [Updated] (KAFKA-5325) Connection Lose during Kafka Kerberos Renewal process

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5325: --- Fix Version/s: 0.11.0.0 > Connection Lose during Kafka Kerberos Renewal process >

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5355: --- Status: In Progress (was: Patch Available) > Broker returns messages beyond "latest stable offset" to

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5355: --- Status: Patch Available (was: Open) > Broker returns messages beyond "latest stable offset" to transa

[jira] [Commented] (KAFKA-5347) OutOfSequence error should be fatal

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035883#comment-16035883 ] Ismael Juma commented on KAFKA-5347: [~apurva] [~hachikuji] This issue has no "Fix ver

[jira] [Updated] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4815: --- Fix Version/s: (was: 0.11.1.0) 0.11.0.0 > Idempotent/transactional Producer Che

[jira] [Updated] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4815: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Idempotent/transactional Producer Che

[jira] [Commented] (KAFKA-5020) Update protocol documentation to mention message format v2

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035878#comment-16035878 ] Ismael Juma commented on KAFKA-5020: I reduced the priority to "Critical" because this

[jira] [Commented] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035879#comment-16035879 ] Ismael Juma commented on KAFKA-5021: Since this is a website update, it doesn't have t

[jira] [Updated] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5021: --- Priority: Critical (was: Blocker) > Update Message Delivery Semantics section to take into account KI

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

2017-06-03 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5020: --- Priority: Critical (was: Blocker) > Update protocol documentation to mention message format v2 >

[jira] [Assigned] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4291: -- Assignee: Mickael Maison (was: Ismael Juma) > TopicCommand --describe shows topics marked for

[jira] [Commented] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035841#comment-16035841 ] Ismael Juma commented on KAFKA-5355: We merged [~hachikuji]'s commit that should fix t

[jira] [Resolved] (KAFKA-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5374. Resolution: Fixed > AdminClient gets "server returned information about unknown correlation ID" > w

[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5019: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3212

[jira] [Commented] (KAFKA-5272) Improve validation for Describe/Alter Configs (KIP-133)

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035728#comment-16035728 ] Ismael Juma commented on KAFKA-5272: I will merge AlterConfigPolicy soon. The rest of

[jira] [Resolved] (KAFKA-5373) ConsoleConsumer prints out object addresses rather than what is expected

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5373. Resolution: Fixed Issue resolved by pull request 3218 [https://github.com/apache/kafka/pull/3218] >

[jira] [Updated] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4595: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.0 > Controller send thread can't stop whe

[jira] [Resolved] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4595. Resolution: Fixed Assignee: Onur Karaman > Controller send thread can't stop when broker chang

[jira] [Updated] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5236: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3205

[jira] [Commented] (KAFKA-3704) Improve mechanism for compression stream block size selection in KafkaProducer

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035424#comment-16035424 ] Ismael Juma commented on KAFKA-3704: The Snappy block size for producer and broker wil

[jira] [Commented] (KAFKA-5148) Add configurable compression block size to the broker

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035423#comment-16035423 ] Ismael Juma commented on KAFKA-5148: The Snappy block size for producer and broker wil

[jira] [Commented] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035417#comment-16035417 ] Ismael Juma commented on KAFKA-5236: Thanks for verifying [~nickt]. > Regression in o

[jira] [Updated] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3264: --- Fix Version/s: (was: 0.11.1.0) > Mark the old Scala consumer and related classes as deprecated > -

[jira] [Updated] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3264: --- Resolution: Fixed Fix Version/s: 0.11.1.0 Status: Resolved (was: Patch Available) I

[jira] [Updated] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5236: --- Assignee: Ismael Juma Status: Patch Available (was: Open) > Regression in on-disk log size when

[jira] [Updated] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5282: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Transactions integration test: Us

[jira] [Resolved] (KAFKA-5365) Fix regression in compressed message iteration affecting magic v0 and v1

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5365. Resolution: Fixed > Fix regression in compressed message iteration affecting magic v0 and v1 > -

[jira] [Updated] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5311: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3199

[jira] [Updated] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5032: --- Description: It's worth noting that the new behaviour for uncompressed messages is the same as the ex

[jira] [Comment Edited] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034279#comment-16034279 ] Ismael Juma edited comment on KAFKA-5032 at 6/2/17 7:35 AM: I

[jira] [Commented] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034279#comment-16034279 ] Ismael Juma commented on KAFKA-5032: I looked into the config change and it looks like

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034264#comment-16034264 ] Ismael Juma commented on KAFKA-4595: Bumping the fix version until we get confirmation

[jira] [Updated] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4595: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Controller send thread can't stop whe

[jira] [Updated] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5032: --- Labels: documentation exactly-once (was: exactly-once) > Think through implications of max.message.si

[jira] [Assigned] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5032: -- Assignee: Ismael Juma > Think through implications of max.message.size affecting record batches

[jira] [Assigned] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5032: -- Assignee: (was: Ismael Juma) > Think through implications of max.message.size affecting rec

[jira] [Commented] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034259#comment-16034259 ] Ismael Juma commented on KAFKA-5026: Moving this to 0.11.0.1. If we somehow have time

[jira] [Updated] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5026: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > DebuggingConsumerId and DebuggingMess

[jira] [Commented] (KAFKA-5284) Add tools and metrics to diagnose problems with the idempotent producer and transactions

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034258#comment-16034258 ] Ismael Juma commented on KAFKA-5284: I'm moving this to 0.11.0.1 given the current tim

[jira] [Updated] (KAFKA-5284) Add tools and metrics to diagnose problems with the idempotent producer and transactions

2017-06-02 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5284: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Add tools and metrics to diagnose pro

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034042#comment-16034042 ] Ismael Juma commented on KAFKA-1595: [~onurkaraman], I had trouble getting people to r

[jira] [Resolved] (KAFKA-2358) Cluster collection returning methods should never return null

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2358. Resolution: Fixed > Cluster collection returning methods should never return null >

[jira] [Resolved] (KAFKA-5345) Some socket connections not closed after restart of Kafka Streams

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5345. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3195 [https://github

[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5293: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3174

[jira] [Updated] (KAFKA-5204) Connect needs to validate Connector type during instantiation

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5204: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Connect needs to validate Connector t

[jira] [Comment Edited] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033577#comment-16033577 ] Ismael Juma edited comment on KAFKA-5054 at 6/1/17 8:00 PM: Th

[jira] [Updated] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5054: --- Priority: Critical (was: Major) > ChangeLoggingKeyValueByteStore delete and putIfAbsent should be syn

[jira] [Updated] (KAFKA-4928) Add integration test for DumpLogSegments

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4928: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Add integration test for DumpLogSegme

[jira] [Updated] (KAFKA-5018) LogCleaner tests to verify behaviour of message format v2

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5018: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > LogCleaner tests to verify behaviour

[jira] [Updated] (KAFKA-4850) RocksDb cannot use Bloom Filters

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4850: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > RocksDb cannot use Bloom Filters > --

[jira] [Commented] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033577#comment-16033577 ] Ismael Juma commented on KAFKA-5054: This seems important and simple, @guozhangwang, c

[jira] [Updated] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4785: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Records from internal repartitioning

[jira] [Updated] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4665: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Inconsistent handling of non-existing

[jira] [Resolved] (KAFKA-2818) Clean up Controller Object on forced Resignation

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2818. Resolution: Fixed Fix Version/s: 0.11.0.0 I think this is fixed by https://github.com/apache

[jira] [Commented] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033550#comment-16033550 ] Ismael Juma commented on KAFKA-3123: Moving to 0.11.0.1 as there is no PR ready for re

[jira] [Updated] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3123: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Follower Broker cannot start if offse

[jira] [Updated] (KAFKA-5228) Revisit Streams DSL JavaDocs

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5228: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Revisit Streams DSL JavaDocs > --

[jira] [Updated] (KAFKA-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5150: --- Fix Version/s: 0.11.0.0 > LZ4 decompression is 4-5x slower than Snappy on small batches / messages > -

[jira] [Updated] (KAFKA-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5150: --- Resolution: Fixed Fix Version/s: (was: 0.11.0.0) 0.10.2.2 Stat

[jira] [Updated] (KAFKA-5360) Down-converted uncompressed batches should respect fetch offset

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5360: --- Summary: Down-converted uncompressed batches should respect fetch offset (was: Down-converted uncompr

[jira] [Updated] (KAFKA-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5316: --- Fix Version/s: 0.10.2.2 > Log cleaning can increase message size and cause cleaner to crash with buffe

[jira] [Created] (KAFKA-5360) Down-converted uncompressed batches should respect requested offset

2017-06-01 Thread Ismael Juma (JIRA)
Ismael Juma created KAFKA-5360: -- Summary: Down-converted uncompressed batches should respect requested offset Key: KAFKA-5360 URL: https://issues.apache.org/jira/browse/KAFKA-5360 Project: Kafka

[jira] [Commented] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

2017-06-01 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032653#comment-16032653 ] Ismael Juma commented on KAFKA-5322: Btw, because this changes the protocol, it would

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032555#comment-16032555 ] Ismael Juma commented on KAFKA-5357: The other option, which is better if possible, is

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032552#comment-16032552 ] Ismael Juma commented on KAFKA-5357: Even if we do that, it's still possible to overfl

[jira] [Commented] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032502#comment-16032502 ] Ismael Juma commented on KAFKA-5322: I prefer option 2 as well. > Resolve AddPartitio

[jira] [Updated] (KAFKA-5291) AdminClient should not trigger auto creation of topics

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5291: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3098

[jira] [Updated] (KAFKA-4487) Tests should be run in Jenkins with INFO or DEBUG level

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4487: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Tests should be run in Jenkins with I

[jira] [Updated] (KAFKA-4628) Support KTable/GlobalKTable Joins

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4628: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Support KTable/GlobalKTable Joins > -

[jira] [Updated] (KAFKA-5356) Producer with transactionalId should be able to send outside of a transaction

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5356: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Producer with transactionalId should

[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5293: --- Status: Patch Available (was: Open) > Do not apply exponential backoff if users have overridden recon

[jira] [Updated] (KAFKA-5353) baseTimestamp should always have a create timestamp

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5353: --- Summary: baseTimestamp should always have a create timestamp (was: Set baseTimestamp correctly if log

[jira] [Updated] (KAFKA-5353) baseTimestamp should always have a create timestamp

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5353: --- Description: This makes the case where we build the records from scratch consistent with the case wher

[jira] [Resolved] (KAFKA-5353) Set baseTimestamp correctly if log append time and no broker recompression

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5353. Resolution: Fixed Issue resolved by pull request 3177 [https://github.com/apache/kafka/pull/3177] >

[jira] [Updated] (KAFKA-5112) Trunk compatibility tests should test against 0.10.2

2017-05-31 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5112: --- Status: Patch Available (was: Open) > Trunk compatibility tests should test against 0.10.2 >

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