[jira] [Commented] (KAFKA-4593) Task migration during rebalance callback process could lead the obsoleted task's IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982470#comment-15982470 ] Damian Guy commented on KAFKA-4593: --- Is this even possible? I.e, thread A would have the

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congratulations Rajini !!! Well deserved -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour,

Re: [VOTE] KIP-114: KTable state stores and improved semantics

Hello, This KIP is now approved. The votes were: Binding +1s: Guozhang, Sriram, Jay Non-binding +1s: Matthias, Bill, Damian. Many thanks Eno > On Apr 22, 2017, at 4:29 PM, Jay Kreps wrote: > > +1 Very well thought out. > > -Jay > > On Fri, Apr 21, 2017 at 10:39 AM Eno Thereska > wrote: >

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congratulation Rajini ! Great news On Tue, Apr 25, 2017 at 8:54 AM, Edoardo Comar wrote: > Congratulations Rajini !!! > Well deserved > -- > Edoardo Comar > IBM MessageHub > eco...@uk.ibm.com > IBM UK Ltd, Hursley Park, SO21 2JN > > IBM United Kingd

[jira] [Commented] (KAFKA-4879) KafkaConsumer.position may hang forever when deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982598#comment-15982598 ] huxi commented on KAFKA-4879: - [~guozhang] What about KafkaConsumer.pollOnce? Does running tim

[jira] [Created] (KAFKA-5122) Kafka Streams off-heap memory leak

Jon Buffington created KAFKA-5122: - Summary: Kafka Streams off-heap memory leak Key: KAFKA-5122 URL: https://issues.apache.org/jira/browse/KAFKA-5122 Project: Kafka Issue Type: Bug

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congrats On Tue, 25 Apr 2017 at 09:57, Mickael Maison wrote: > Congratulation Rajini ! > Great news > > On Tue, Apr 25, 2017 at 8:54 AM, Edoardo Comar wrote: > > Congratulations Rajini !!! > > Well deserved > > -- > > Edoardo Comar > > IBM MessageH

[GitHub] kafka pull request #2911: MINOR: Improve information in assert failure for t...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2911 MINOR: Improve information in assert failure for testMetricCollectionAfterShutdown This test is failing consistently in https://jenkins.confluent.io/job/kafka-trunk/, but nowhere else. I ran this

Re: [DISCUSS] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Even though it's a really small KIP, I'm sure people have ideas how to improved it. If there are no comments, I'll start a vote next week On Thu, Mar 30, 2017 at 5:39 PM, Mickael Maison wrote: > Hi all, > > We created KIP-137: Enhance TopicCommand --describe to show topics > marked for deletion

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982716#comment-15982716 ] Dhana commented on KAFKA-5070: -- Hi Matthias J. Sax, Thanks for reponse. We tried the 0.10.2.

Re: [DISCUSS] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Thanks for the KIP. Would it make sense for MarkedForDeletion to be before `Configs`? I can see arguments both ways, so I was wondering what your thoughts were? Ismael On Thu, Mar 30, 2017 at 5:39 PM, Mickael Maison wrote: > Hi all, > > We created KIP-137: Enhance TopicCommand --describe to sho

Re: [ANNOUNCE] New committer: Rajini Sivaram

Thanks everyone! It has been a pleasure working with all of you in the Kafka community. Many thanks to the PMC for this exciting opportunity. Regards, Rajini On Tue, Apr 25, 2017 at 10:51 AM, Damian Guy wrote: > Congrats > On Tue, 25 Apr 2017 at 09:57, Mickael Maison > wrote: > > > Congratul

Re: [DISCUSS] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

This is another very small KIP. We've implemented it in our clusters' and found it useful to look at our metrics. More comments welcome; I'd like to do the voting next week. Edo -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congrats! Eno > On Apr 25, 2017, at 12:17 PM, Rajini Sivaram wrote: > > Thanks everyone! > > It has been a pleasure working with all of you in the Kafka community. Many > thanks to the PMC for this exciting opportunity. > > Regards, > > Rajini > > On Tue, Apr 25, 2017 at 10:51 AM, Damian Guy

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congrats, Rajini:) 2017-04-25 13:31 GMT+02:00 Eno Thereska : > Congrats! > > Eno > > On Apr 25, 2017, at 12:17 PM, Rajini Sivaram > wrote: > > > > Thanks everyone! > > > > It has been a pleasure working with all of you in the Kafka community. > Many > > thanks to the PMC for this exciting opport

Re: [DISCUSS] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

Thanks for the KIP. I think it makes sense to have those tags. My only question is regarding the compatibility impact. We don't have a good compatibility story when it comes to adding tags to existing metrics since the JmxReporter adds the tags to the object name. Ismael On Thu, Mar 30, 2017 at 4

[jira] [Assigned] (KAFKA-4879) KafkaConsumer.position may hang forever when deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun reassigned KAFKA-4879: -- Assignee: (was: Armin Braun) > KafkaConsumer.position may hang forever when deleting a topi

[jira] [Created] (KAFKA-5123) Refactor ZkUtils readData* methods

Balint Molnar created KAFKA-5123: Summary: Refactor ZkUtils readData* methods Key: KAFKA-5123 URL: https://issues.apache.org/jira/browse/KAFKA-5123 Project: Kafka Issue Type: Bug

[jira] [Work started] (KAFKA-5123) Refactor ZkUtils readData* methods

[ https://issues.apache.org/jira/browse/KAFKA-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5123 started by Balint Molnar. > Refactor ZkUtils readData* methods > --- > >

[jira] [Work started] (KAFKA-5025) FetchRequestTest should use batches with more than one message

[ https://issues.apache.org/jira/browse/KAFKA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5025 started by Armin Braun. -- > FetchRequestTest should use batches with more than one message > --

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

[ https://issues.apache.org/jira/browse/KAFKA-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4928 started by Armin Braun. -- > Add integration test for DumpLogSegments >

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

[ https://issues.apache.org/jira/browse/KAFKA-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun updated KAFKA-5018: --- Status: Patch Available (was: Open) > LogCleaner tests to verify behaviour of message format v2 > ---

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

[ https://issues.apache.org/jira/browse/KAFKA-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun updated KAFKA-4928: --- Status: Patch Available (was: In Progress) > Add integration test for DumpLogSegments > -

[jira] [Work stopped] (KAFKA-5025) FetchRequestTest should use batches with more than one message

[ https://issues.apache.org/jira/browse/KAFKA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5025 stopped by Armin Braun. -- > FetchRequestTest should use batches with more than one message > --

[jira] [Assigned] (KAFKA-5025) FetchRequestTest should use batches with more than one message

[ https://issues.apache.org/jira/browse/KAFKA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun reassigned KAFKA-5025: -- Assignee: (was: Armin Braun) > FetchRequestTest should use batches with more than one messa

[jira] [Created] (KAFKA-5124) shouldInnerLeftJoin unit test fails

Eno Thereska created KAFKA-5124: --- Summary: shouldInnerLeftJoin unit test fails Key: KAFKA-5124 URL: https://issues.apache.org/jira/browse/KAFKA-5124 Project: Kafka Issue Type: Bug Com

[jira] [Commented] (KAFKA-5124) shouldInnerLeftJoin unit test fails

[ https://issues.apache.org/jira/browse/KAFKA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982909#comment-15982909 ] Armin Braun commented on KAFKA-5124: Trying this one, I can reproduce it locally :) >

[jira] [Assigned] (KAFKA-5124) shouldInnerLeftJoin unit test fails

[ https://issues.apache.org/jira/browse/KAFKA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun reassigned KAFKA-5124: -- Assignee: Armin Braun > shouldInnerLeftJoin unit test fails > -

[jira] [Updated] (KAFKA-5124) shouldInnerLeftJoin unit test fails

[ https://issues.apache.org/jira/browse/KAFKA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun updated KAFKA-5124: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-2054 > shouldInnerLeftJoin unit test fails > --

[jira] [Commented] (KAFKA-5124) shouldInnerLeftJoin unit test fails

[ https://issues.apache.org/jira/browse/KAFKA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982917#comment-15982917 ] Eno Thereska commented on KAFKA-5124: - Thanks [~original-brownbear] > shouldInnerLeft

[jira] [Assigned] (KAFKA-5025) FetchRequestTest should use batches with more than one message

[ https://issues.apache.org/jira/browse/KAFKA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Chaudhary reassigned KAFKA-5025: -- Assignee: Umesh Chaudhary > FetchRequestTest should use batches with more than one mess

[jira] [Commented] (KAFKA-5025) FetchRequestTest should use batches with more than one message

[ https://issues.apache.org/jira/browse/KAFKA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982953#comment-15982953 ] Umesh Chaudhary commented on KAFKA-5025: [~ijuma], taking this one to start my con

[GitHub] kafka pull request #2858: KAFKA-438: Code cleanup in MessageTest

Github user jozi-k closed the pull request at: https://github.com/apache/kafka/pull/2858 --- 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-438) Code cleanup in MessageTest

[ https://issues.apache.org/jira/browse/KAFKA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982964#comment-15982964 ] Jozef Koval commented on KAFKA-438: --- Can be closed as MessageTest will be deleted soon.

[jira] [Commented] (KAFKA-438) Code cleanup in MessageTest

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

[jira] [Updated] (KAFKA-5120) Several controller metrics block if controller lock is held by another thread

[ https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Carey-Smith updated KAFKA-5120: --- Description: We have been tracking latency issues surrounding queries to Controller MBeans. U

[jira] [Commented] (KAFKA-5120) Several controller metrics block if controller lock is held by another thread

[ https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982994#comment-15982994 ] Tim Carey-Smith commented on KAFKA-5120: [~onurkaraman] Ah, thanks! That patch loo

[jira] [Commented] (KAFKA-5120) Several controller metrics block if controller lock is held by another thread

[ https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983009#comment-15983009 ] Ismael Juma commented on KAFKA-5120: [~halorgium], if everything goes well, that PR sh

[GitHub] kafka pull request #2912: KAFKA-4942 Fix commitTimeoutMs being set before th...

GitHub user 56quarters opened a pull request: https://github.com/apache/kafka/pull/2912 KAFKA-4942 Fix commitTimeoutMs being set before the commit actually started This fixes KAFKA-4942 This supersededs #2730 /cc @simplesteph @gwenshap @ewencp You can merge this p

[jira] [Commented] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

[ https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983038#comment-15983038 ] ASF GitHub Bot commented on KAFKA-4942: --- GitHub user 56quarters opened a pull reques

[jira] [Commented] (KAFKA-4970) Add a 'ProducerIdResource' to enable authorization for generating producer ids

[ https://issues.apache.org/jira/browse/KAFKA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983095#comment-15983095 ] Ismael Juma commented on KAFKA-4970: In the KIP we mention `ProducerTransactionalId` a

Re: [DISCUSS] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Thanks for the KIP Mickael. Looks good. I also prefer 'MarkedForDeletion' before 'Configs'. --Vahid From: Ismael Juma To: dev@kafka.apache.org Date: 04/25/2017 04:15 AM Subject:Re: [DISCUSS] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion Sent by:

[GitHub] kafka pull request #2913: Kafka-4994: Fix findbug warnings about OffsetStora...

GitHub user johnma14 opened a pull request: https://github.com/apache/kafka/pull/2913 Kafka-4994: Fix findbug warnings about OffsetStorageWriter OffsetStorageWriter is not a thread-safe class and should be accessed only from a Task's processing thread. The WorkerSourceTask class

[jira] [Created] (KAFKA-5125) controlled.shutdown.enable=true leads blocking some time during shutdown when the broker is the only remaining broker

Zeynep Arikoglu created KAFKA-5125: -- Summary: controlled.shutdown.enable=true leads blocking some time during shutdown when the broker is the only remaining broker Key: KAFKA-5125 URL: https://issues.apache.org/j

[jira] [Commented] (KAFKA-4970) Add a 'ProducerIdResource' to enable authorization for generating producer ids

[ https://issues.apache.org/jira/browse/KAFKA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983276#comment-15983276 ] Apurva Mehta commented on KAFKA-4970: - This is different. This is to make the 'produc

[GitHub] kafka pull request #2659: KAFKA-4840 : BufferPool errors can cause buffer po...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2659 --- 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-4840) There are are still cases where producer buffer pool will not remove waiters.

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

[VOTE] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Hi, I would like to start the voting on KIP-126. The KIP is intended to solve the problem that RecordTooLargeExceptions are thrown from the producer due to inaccurate estimation of the compression ratio. The solution is to split and resend the over sized batches if possible. A new metric is introd

[jira] [Resolved] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov resolved KAFKA-4144. --- Resolution: Fixed Reviewer: Matthias J. Sax > Allow per stream/table timestamp extractor

[jira] [Closed] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov closed KAFKA-4144. - > Allow per stream/table timestamp extractor > -- > >

[jira] [Created] (KAFKA-5126) Implement KIP-98 transactional methods in the MockProducer

Apurva Mehta created KAFKA-5126: --- Summary: Implement KIP-98 transactional methods in the MockProducer Key: KAFKA-5126 URL: https://issues.apache.org/jira/browse/KAFKA-5126 Project: Kafka Issue

Re: [VOTE] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

+1 (non-binding) On Tue, Apr 25, 2017 at 10:42 AM, Becket Qin wrote: > Hi, > > I would like to start the voting on KIP-126. The KIP is intended to solve > the problem that RecordTooLargeExceptions are thrown from the producer due > to inaccurate estimation of the compression ratio. The solution

Re: [VOTE] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

I just updated the KIP name to reflect the actual proposal. I'll close this vote and start another one to avoid confusion. On Tue, Apr 25, 2017 at 12:27 PM, Dong Lin wrote: > +1 (non-binding) > > On Tue, Apr 25, 2017 at 10:42 AM, Becket Qin wrote: > > > Hi, > > > > I would like to start the vot

[VOTE] KIP-126 - Allow KafkaProducer to split and resend oversized batches.

Hi, I would like to start the voting on KIP-126. The KIP is intended to solve the problem that RecordTooLargeExceptions are thrown from the producer due to inaccurate estimation of the compression ratio. The solution is to split and resend the over sized batches if possible. A new metric is introd

[jira] [Commented] (KAFKA-5124) shouldInnerLeftJoin unit test fails

[ https://issues.apache.org/jira/browse/KAFKA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983498#comment-15983498 ] Matthias J. Sax commented on KAFKA-5124: I guess is related to https://issues.apac

[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983504#comment-15983504 ] Matthias J. Sax commented on KAFKA-4144: [~jeyhunkarimov] Why did you close the PR

[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983515#comment-15983515 ] Jeyhun Karimov commented on KAFKA-4144: --- [~mjsax] I am sorry, I didn't read your ema

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov updated KAFKA-4144: -- Status: Reopened (was: Closed) > Allow per stream/table timestamp extractor > -

[jira] [Updated] (KAFKA-4994) Fix findbugs warning about OffsetStorageWriter#currentFlushId

[ https://issues.apache.org/jira/browse/KAFKA-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariam John updated KAFKA-4994: --- Status: Open (was: Patch Available) > Fix findbugs warning about OffsetStorageWriter#currentFlushId >

[GitHub] kafka pull request #2906: Kafka-4994 Fix findbug warnings about OffsetStorag...

Github user johnma14 closed the pull request at: https://github.com/apache/kafka/pull/2906 --- 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 en

[GitHub] kafka pull request #2913: KAFKA-4994: Fix findbug warnings about OffsetStora...

Github user johnma14 closed the pull request at: https://github.com/apache/kafka/pull/2913 --- 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 en

[jira] [Commented] (KAFKA-5124) shouldInnerLeftJoin unit test fails

[ https://issues.apache.org/jira/browse/KAFKA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983539#comment-15983539 ] Armin Braun commented on KAFKA-5124: @msjax certainly looks like it at least. I only f

[jira] [Commented] (KAFKA-4994) Fix findbugs warning about OffsetStorageWriter#currentFlushId

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

[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983547#comment-15983547 ] Matthias J. Sax commented on KAFKA-4144: No problem :) > Allow per stream/table t

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4144: --- Fix Version/s: 0.11.0.0 > Allow per stream/table timestamp extractor > ---

Re: [VOTE] KIP-126 - Allow KafkaProducer to split and resend oversized batches.

+1 (non-binding) On Tue, Apr 25, 2017 at 12:33 PM, Becket Qin wrote: > Hi, > > I would like to start the voting on KIP-126. The KIP is intended to solve > the problem that RecordTooLargeExceptions are thrown from the producer due > to inaccurate estimation of the compression ratio. The solution

[GitHub] kafka pull request #2914: KAFKA-4994: Fix findbug warnings about OffsetStora...

GitHub user johnma14 opened a pull request: https://github.com/apache/kafka/pull/2914 KAFKA-4994: Fix findbug warnings about OffsetStorageWriter OffsetStorageWriter is not a thread-safe class and should be accessed only from a Task's processing thread. The WorkerSourceTask class

[jira] [Commented] (KAFKA-4994) Fix findbugs warning about OffsetStorageWriter#currentFlushId

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

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Dear all, I am closing this vote now. The KIP got accepted with +3 binding (Guozhang, Ewen, Gwen) Thanks all (especially for Mathias) for guiding me throughout my first KIP. Cheers, Jeyhun On Mon, Apr 24, 2017 at 9:32 PM Thomas Becker wrote: > +1 (non-binding) > > On Tue, 2017-02-28 at 08:5

[jira] [Commented] (KAFKA-4994) Fix findbugs warning about OffsetStorageWriter#currentFlushId

[ https://issues.apache.org/jira/browse/KAFKA-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983633#comment-15983633 ] Mariam John commented on KAFKA-4994: [~cmccabe] [~ewencp] A fix for this issue is read

[jira] [Updated] (KAFKA-4994) Fix findbugs warning about OffsetStorageWriter#currentFlushId

[ https://issues.apache.org/jira/browse/KAFKA-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariam John updated KAFKA-4994: --- Status: Patch Available (was: Open) > Fix findbugs warning about OffsetStorageWriter#currentFlushId >

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4144: --- Status: Patch Available (was: Reopened) > Allow per stream/table timestamp extractor > --

Re: [VOTE] KIP-126 - Allow KafkaProducer to split and resend oversized batches.

+1 On Tue, Apr 25, 2017 at 4:43 PM, Dong Lin wrote: > +1 (non-binding) > > On Tue, Apr 25, 2017 at 12:33 PM, Becket Qin wrote: > > > Hi, > > > > I would like to start the voting on KIP-126. The KIP is intended to solve > > the problem that RecordTooLargeExceptions are thrown from the producer >

[GitHub] kafka pull request #2911: MINOR: Improve information in assert failure for t...

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/2911 --- 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 enabl

[GitHub] kafka pull request #2911: MINOR: Improve information in assert failure for t...

GitHub user ijuma reopened a pull request: https://github.com/apache/kafka/pull/2911 MINOR: Improve information in assert failure for testMetricCollectionAfterShutdown This test is failing consistently in https://jenkins.confluent.io/job/kafka-trunk/, but nowhere else. I ran th

[GitHub] kafka pull request #2911: MINOR: Improve information in assert failure for t...

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/2911 --- 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 enabl

[jira] [Commented] (KAFKA-5119) Transient test failure SocketServerTest.testMetricCollectionAfterShutdown

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

[GitHub] kafka pull request #2915: KAFKA-5119: Improve information in assert failure ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2915 KAFKA-5119: Improve information in assert failure for testMetricCollectionAfterShutdown This test is failing consistently in https://jenkins.confluent.io/job/kafka-trunk/, but nowhere else. I ran

[jira] [Commented] (KAFKA-4905) StreamPartitionAssignor doesn't respect subscriptions to assign partitions.

[ https://issues.apache.org/jira/browse/KAFKA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983803#comment-15983803 ] Matthias J. Sax commented on KAFKA-4905: [~stevenschlansker] I just stubbled over

Re: [DISCUSS] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Having "MarkedForDeletion" before "Configs" may break anyone who is parsing this output, since they may be expecting the 4th string to be "Configs". I know that the Compatibility section already says that people parsing this may have to adjust their parsing logic, so maybe that covers my concern

[GitHub] kafka pull request #2916: WIP: Avoid FileInputStream and FileOutputStream

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2916 WIP: Avoid FileInputStream and FileOutputStream You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka no-file-input-stream Alternatively yo

[GitHub] kafka pull request #2895: KAFKA-5111: Improve internal Task APIs

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2895 --- 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-5111) Improve internal Task APIs

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

[jira] [Commented] (KAFKA-5111) Improve internal Task APIs

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

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

See Changes: [becket.qin] KAFKA-4840; BufferPool errors can cause buffer pool to go into a bad [wangguoz] KAFKA-5111: Improve internal Task APIs of Streams -- [...trunca

[GitHub] kafka pull request #2917: Kafka 5111 code cleanup follow up

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2917 Kafka 5111 code cleanup follow up - mainly moving methods - also improved logging You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Thanks for your work and for driving this, Jeyhun! :-) -Michael On Tue, Apr 25, 2017 at 11:11 PM, Jeyhun Karimov wrote: > Dear all, > > I am closing this vote now. The KIP got accepted with > > +3 binding (Guozhang, Ewen, Gwen) > > Thanks all (especially for Mathias) for guiding me throughout

[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984230#comment-15984230 ] Michael Noll commented on KAFKA-4144: - As part of this work we should also update the