Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Hi there, Sorry for the late reply, I was out this past week. Looks like good progress was made with the discussions either way. Let me recap a couple of points I saw into one big reply: 1. Jan mentioned CRC errors. I think this is a good point. As these happen in Kafka, before Kafka Streams g

[jira] [Commented] (KAFKA-5377) Kafka server process crashing due to access violation (caused by log cleaner)

[ https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036741#comment-16036741 ] Rajini Sivaram commented on KAFKA-5377: --- Perhaps the corruption and the failures are

[jira] [Commented] (KAFKA-5369) Producer hangs on metadata fetch from broker in security authorization related failures and no meaningful exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036785#comment-16036785 ] Rajini Sivaram commented on KAFKA-5369: --- [~Koelli] Diagnostics were improved under K

[jira] [Commented] (KAFKA-5346) Kafka Producer Failure After Idle Time

[ https://issues.apache.org/jira/browse/KAFKA-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036795#comment-16036795 ] Rajini Sivaram commented on KAFKA-5346: --- Broker closes the connection after idle tim

[GitHub] kafka pull request #3236: MINOR: Default GroupInitialRebalanceDelayMsProp to...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3236 MINOR: Default GroupInitialRebalanceDelayMsProp to 0 and OffsetsTopicPartitionsProp to 5 in tests This should make tests faster. Tests that require specific values can override these values. You can

[GitHub] kafka pull request #3237: KAFKA-4948: Create offsets topic in setup of Descr...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3237 KAFKA-4948: Create offsets topic in setup of DescribeConsumerGroupTest This should fix transient failures due to timeouts caused by slow auto creation of the offsets topic. Also simplified

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

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

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

[ 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-4948) Failure in kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGroupWithNoMembersWithNewConsumer

[ https://issues.apache.org/jira/browse/KAFKA-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4948: --- Fix Version/s: 0.11.0.0 > Failure in > kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGrou

[GitHub] kafka pull request #3236: MINOR: Default GroupInitialRebalanceDelayMsProp to...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3236 --- 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 enab

Re: [VOTE] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

+1 (non binding) Dong, thanks for the KIP :-) -- Edoardo Comar IBM Message Hub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN From: Michal Borowiecki To: dev@kafka.apache.org Date: 02/06/2017 10:25 Subject:Re: [VOTE] KIP-16

Re: [VOTE] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

Thanks for the KIP. +1 -Bill On Mon, Jun 5, 2017 at 8:51 AM, Edoardo Comar wrote: > +1 (non binding) > > Dong, thanks for the KIP :-) > -- > Edoardo Comar > IBM Message Hub > eco...@uk.ibm.com > IBM UK Ltd, Hursley Park, SO21 2JN > > > > > From:

[jira] [Created] (KAFKA-5379) ProcessorContext.appConfigs() should return parsed/validated values

Tommy Becker created KAFKA-5379: --- Summary: ProcessorContext.appConfigs() should return parsed/validated values Key: KAFKA-5379 URL: https://issues.apache.org/jira/browse/KAFKA-5379 Project: Kafka

[jira] [Created] (KAFKA-5380) Transient test failure: KafkaConsumerTest.testChangingRegexSubscription

Rajini Sivaram created KAFKA-5380: - Summary: Transient test failure: KafkaConsumerTest.testChangingRegexSubscription Key: KAFKA-5380 URL: https://issues.apache.org/jira/browse/KAFKA-5380 Project: Kafk

[jira] [Updated] (KAFKA-5377) Kafka server process crashing due to access violation (caused by log cleaner)

[ https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus B updated KAFKA-5377: Environment: Windows 2008 R2, Intel Xeon CPU, 64 GB RAM 4 Disk Drives (C for software, D for log files, E/F

[jira] [Commented] (KAFKA-5377) Kafka server process crashing due to access violation (caused by log cleaner)

[ https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037037#comment-16037037 ] Markus B commented on KAFKA-5377: - It's not a diskspace issue. - The E/F drives that are d

[jira] [Updated] (KAFKA-5377) Kafka server process crashing due to access violation (caused by log cleaner)

[ https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus B updated KAFKA-5377: Description: We are running Kafka in a 2 x broker cluster configuration on Windows, and overall it has been

[GitHub] kafka pull request #3219: KAFKA-5374. AdminClient gets "server returned info...

Github user cmccabe closed the pull request at: https://github.com/apache/kafka/pull/3219 --- 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 ena

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

[ https://issues.apache.org/jira/browse/KAFKA-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037175#comment-16037175 ] ASF GitHub Bot commented on KAFKA-5374: --- Github user cmccabe closed the pull request

[GitHub] kafka pull request #3238: KAFKA-5380: Fix transient failure in KafkaConsumer...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3238 KAFKA-5380: Fix transient failure in KafkaConsumerTest, close consumers In `KafkaConsumer#testChangingRegexSubscription`, keep metadata updated with both topics since heartbeat thread may remo

[jira] [Commented] (KAFKA-5380) Transient test failure: KafkaConsumerTest.testChangingRegexSubscription

[ https://issues.apache.org/jira/browse/KAFKA-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037295#comment-16037295 ] ASF GitHub Bot commented on KAFKA-5380: --- GitHub user rajinisivaram opened a pull req

[GitHub] kafka pull request #3215: MINOR: Adding deprecated KTable methods to docs fr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3215 --- 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 enab

Fwd: Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Should go to dev list, too. Forwarded Message Subject: Re: [DISCUSS]: KIP-161: streams record processing exception handlers Date: Mon, 5 Jun 2017 19:19:42 +0200 From: Jan Filipiak Reply-To: us...@kafka.apache.org To: us...@kafka.apache.org Hi just my few thoughts On 05.06.20

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

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5357. -- Resolution: Fixed Issue resolved by pull request 3192 [https://github.com/apache/kafka/pull/3192

[GitHub] kafka pull request #3192: KAFKA-5357: StackOverFlow error in transaction coo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3192 --- 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 enab

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

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

[jira] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5366: Fix Version/s: (was: 0.11.0.1) 0.11.0.0 > Add cases for concurrent transactio

[jira] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5366: Priority: Blocker (was: Major) > Add cases for concurrent transactional reads and writes in system

[jira] [Commented] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037403#comment-16037403 ] Apurva Mehta commented on KAFKA-5366: - [~ijuma] I originally marked this as a 'Major'

[jira] [Comment Edited] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037403#comment-16037403 ] Apurva Mehta edited comment on KAFKA-5366 at 6/5/17 6:59 PM: -

[GitHub] kafka pull request #3239: KAFKA-5376: Ensure aborted transactions are propag...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3239 KAFKA-5376: Ensure aborted transactions are propagated in DelayedFetch You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-5

[jira] [Commented] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

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

[jira] [Updated] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

[ https://issues.apache.org/jira/browse/KAFKA-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5376: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > Transactions: Concurrent transac

[jira] [Updated] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

[ https://issues.apache.org/jira/browse/KAFKA-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5376: --- Status: Patch Available (was: Open) > Transactions: Concurrent transactional consumer reads a

Build failed in Jenkins: kafka-0.11.0-jdk7 #100

See Changes: [wangguoz] KAFKA-5357: capture unexpected exception in txn marker sender thread and -- Started by an SCM change Started by an SCM change [EnvInject] - Loadin

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

[ https://issues.apache.org/jira/browse/KAFKA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5378 started by Jason Gustafson. -- > Last Stable Offset not returned in Fetch request >

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi, Sorry for late reply. Just to make everybody in sync, the current version of KIP supports lambdas. "withKey" (ValueMapperWithKey) interfaces are independent, meaning they do not extend from "withoutKey" (ValueMapper) interfaces. I agree with Guozhang, and I am personally a bit reluctant to

[jira] [Created] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

Jeff Widman created KAFKA-5381: -- Summary: ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler) Key: KAFKA-5381 URL: https://issues.apache.org/jira/browse/KAFKA-538

[jira] [Updated] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5381: --- Description: We have a 6 node cluster of 0.10.0.1 brokers. Broker 4 had a hardware problem, so we re-

[jira] [Updated] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5381: --- Description: We have a 6 node cluster of 0.10.0.1 brokers. Broker 4 had a hardware problem, so we re-

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi, Thanks for your comments Matthias and Guozhang. Below I mention the quick summary of the main alternatives we looked at to introduce the Rich functions (I will refer to it as Rich functions until we find better/another name). Initially the proposed alternatives was not backwards-compatible, s

Re: KIP-160 - Augment KStream.print() to allow users pass in extra parameters in the printed string

I agree with Matthias's comment. Constructing RecordContext with more metadata seems more feasible for me. Cheers, Jeyun On Mon, Jun 5, 2017 at 7:47 AM Matthias J. Sax wrote: > Not with the scope of the current discussion. > > So far, we discuss to add `RecordContext`, but the context object we

[jira] [Assigned] (KAFKA-5382) Log recovery can fail if topic names contain one of the index suffixes

[ https://issues.apache.org/jira/browse/KAFKA-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5382: -- Assignee: Jason Gustafson > Log recovery can fail if topic names contain one of the ind

[jira] [Created] (KAFKA-5382) Log recovery can fail if topic names contain one of the index suffixes

Jason Gustafson created KAFKA-5382: -- Summary: Log recovery can fail if topic names contain one of the index suffixes Key: KAFKA-5382 URL: https://issues.apache.org/jira/browse/KAFKA-5382 Project: Kaf

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037820#comment-16037820 ] Xavier Léauté commented on KAFKA-5275: -- Now that describe topic doesn't auto-create t

[jira] [Comment Edited] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037820#comment-16037820 ] Xavier Léauté edited comment on KAFKA-5275 at 6/5/17 11:14 PM: -

[jira] [Updated] (KAFKA-5292) Fix authorization checks in AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5292: --- Summary: Fix authorization checks in AdminClient (was: Update authorization checks in AdminCl

[jira] [Updated] (KAFKA-5292) Fix authorization checks in AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5292: --- Description: Fix authorization checks in AdminClient. (was: AuthorizerIntegrationTest include

[jira] [Commented] (KAFKA-5292) Fix authorization checks in AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037938#comment-16037938 ] Colin P. McCabe commented on KAFKA-5292: * NetworkClient.java: when trace logging

[GitHub] kafka pull request #3240: KAFKA-5292. Fix authorization checks in AdminClien...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3240 KAFKA-5292. Fix authorization checks in AdminClient * NetworkClient.java: when trace logging is enabled, show AbstractResponse Struct objects, rather than just a memory address of the AbstractRespon

[jira] [Commented] (KAFKA-5292) Fix authorization checks in AdminClient

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

[GitHub] kafka pull request #3234: MINOR: Optimise performance of `Topic.validate()`

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3234 --- 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 enab

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

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

[GitHub] kafka pull request #2701: KAFKA-5112: Update compatibility system tests to i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2701 --- 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 enab

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

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

[jira] [Created] (KAFKA-5383) Additional Test Cases for ReplicaManager

Jason Gustafson created KAFKA-5383: -- Summary: Additional Test Cases for ReplicaManager Key: KAFKA-5383 URL: https://issues.apache.org/jira/browse/KAFKA-5383 Project: Kafka Issue Type: Sub-ta

[jira] [Updated] (KAFKA-5383) Additional Test Cases for ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5383: --- Description: KAFKA-5355 and KAFKA-5376 have shown that current testing of ReplicaManager is in

[GitHub] kafka pull request #3239: KAFKA-5376: Ensure aborted transactions are propag...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3239 --- 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 enab

[jira] [Updated] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

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

[jira] [Commented] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

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

[GitHub] kafka pull request #3208: KAFKA-5325: Avoid and handle exceptions for Kerber...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3208 --- 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 enab

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

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

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

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

[GitHub] kafka pull request #3053: KAFKA-5239: Producer buffer pool allocates memory ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3053 --- 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 enab

[jira] [Commented] (KAFKA-5239) Producer buffer pool allocates memory inside a lock.

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

[jira] [Updated] (KAFKA-5292) Fix authorization checks in AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5292: --- Status: Patch Available (was: Open) > Fix authorization checks in AdminClient > -

[jira] [Updated] (KAFKA-5292) Fix authorization checks in AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5292: --- Priority: Blocker (was: Critical) > Fix authorization checks in AdminClient > ---

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

See Changes: [ismael] MINOR: Optimise performance of `Topic.validate()` -- [...truncated 955.59 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[8] PASSE

Build failed in Jenkins: kafka-trunk-jdk8 #1660

See Changes: [ismael] MINOR: Optimise performance of `Topic.validate()` -- [...truncated 2.02 MB...] org.apache.kafka.common.security.scram.ScramMessagesTest > validServe

Jenkins build is back to normal : kafka-0.11.0-jdk7 #101

See

[jira] [Created] (KAFKA-5384) KIP-162: Enable topic deletion by default

Gwen Shapira created KAFKA-5384: --- Summary: KIP-162: Enable topic deletion by default Key: KAFKA-5384 URL: https://issues.apache.org/jira/browse/KAFKA-5384 Project: Kafka Issue Type: Improvement

[GitHub] kafka pull request #3241: KAFKA-5384: Enable topic deletion by default

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/3241 KAFKA-5384: Enable topic deletion by default https://cwiki.apache.org/confluence/display/KAFKA/KIP-162+-+Enable+topic+deletion+by+default You can merge this pull request into a Git repository by r

[jira] [Commented] (KAFKA-5384) KIP-162: Enable topic deletion by default

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

[VOTE] KIP-162: Enable topic deletion by default

Hi, The discussion has been quite positive, so I posted a JIRA, a PR and updated the KIP with the latest decisions. Lets officially vote on the KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-162+-+Enable+topic+deletion+by+default JIRA is here: https://issues.apache.org/jira/browse/KA

Re: [VOTE] KIP-162: Enable topic deletion by default

+1 (non-binding) Thanks. --Vahid From: Gwen Shapira To: "dev@kafka.apache.org" , Users Date: 06/05/2017 09:38 PM Subject:[VOTE] KIP-162: Enable topic deletion by default Hi, The discussion has been quite positive, so I posted a JIRA, a PR and updated the KIP with the late

Jenkins build is back to normal : kafka-trunk-jdk7 #2350

See

Build failed in Jenkins: kafka-0.11.0-jdk7 #102

See Changes: [ismael] KAFKA-5376; Ensure aborted transactions are propagated in DelayedFetch [ismael] KAFKA-5325; Avoid and handle exceptions for Kerberos re-login -- [..

[jira] [Commented] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038146#comment-16038146 ] Apurva Mehta commented on KAFKA-5375: - This is a red herring. The problem was with the

[jira] [Comment Edited] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038146#comment-16038146 ] Apurva Mehta edited comment on KAFKA-5375 at 6/6/17 4:54 AM: -

[jira] [Comment Edited] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038146#comment-16038146 ] Apurva Mehta edited comment on KAFKA-5375 at 6/6/17 4:55 AM: -

[jira] [Comment Edited] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038146#comment-16038146 ] Apurva Mehta edited comment on KAFKA-5375 at 6/6/17 5:00 AM: -

Jenkins build is back to normal : kafka-trunk-jdk8 #1661

See

[GitHub] kafka pull request #3242: KAFKA-5357 follow-up: Yammer metrics, not Kafka Me...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3242 KAFKA-5357 follow-up: Yammer metrics, not Kafka Metrics You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K5357-yammer-met

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

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038229#comment-16038229 ] ASF GitHub Bot commented on KAFKA-5357: --- GitHub user guozhangwang opened a pull requ

[jira] [Created] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

Apurva Mehta created KAFKA-5385: --- Summary: Transactional Producer allows batches to expire and commits transactions regardless Key: KAFKA-5385 URL: https://issues.apache.org/jira/browse/KAFKA-5385 Proje

[jira] [Updated] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

[ https://issues.apache.org/jira/browse/KAFKA-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5385: Description: The transactions system test has revealed a data loss issue. When there is cluster ins

[jira] [Assigned] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5375: --- Assignee: (was: Apurva Mehta) > Transactions: Concurrent transactional consumer loses mes

[jira] [Assigned] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

[ https://issues.apache.org/jira/browse/KAFKA-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5385: --- Assignee: Apurva Mehta > Transactional Producer allows batches to expire and commits transact

[jira] [Commented] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038261#comment-16038261 ] Apurva Mehta commented on KAFKA-5375: - Here is a relevant output from a recent run:

[jira] [Updated] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5375: Attachment: KAFKA-5375.tar.gz Here are all the logs from the last failure. > Transactions: Concurre