[jira] [Updated] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Travers updated KAFKA-4900: Description: We hit this today in one of out three node staging clusters. The exception continues

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925560#comment-15925560 ] Nick Travers commented on KAFKA-4900: - [~onurkaraman] - good to know! Were you able to resolve the

[jira] [Commented] (KAFKA-4885) processstreamwithcachedstatestore and other streams benchmarks fail occasionally

[ https://issues.apache.org/jira/browse/KAFKA-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925521#comment-15925521 ] Guozhang Wang commented on KAFKA-4885: -- As for the fix, I think it could be quite complicated and

[jira] [Commented] (KAFKA-4885) processstreamwithcachedstatestore and other streams benchmarks fail occasionally

[ https://issues.apache.org/jira/browse/KAFKA-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925516#comment-15925516 ] Guozhang Wang commented on KAFKA-4885: -- Looked into the logs, the root cause is actually because the

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925503#comment-15925503 ] Onur Karaman commented on KAFKA-4900: - We hit the same re-election loop issue from

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

See Changes: [wangguoz] KAFKA-4863; Querying window store may return unwanted keys -- [...truncated 1.59 MB...]

[jira] [Created] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

Nick Travers created KAFKA-4900: --- Summary: Brokers stuck in controller re-election loop after failing to register metrics Key: KAFKA-4900 URL: https://issues.apache.org/jira/browse/KAFKA-4900 Project:

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

See Changes: [me] KAFKA-4783: Add ByteArrayConverter (KIP-128) -- [...truncated 888.34 KB...] org.apache.kafka.connect.json.JsonConverterTest > nullSchemaAndMapToJson

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Hi Colin, Thanks for the reply. Please see comments inline. On Tue, Mar 14, 2017 at 5:30 PM, Colin McCabe wrote: > On Tue, Mar 14, 2017, at 13:36, Becket Qin wrote: > > The interface looks good overall. Thanks for the much needed work Colin. > > Thanks, Becket. > > > Just a

[jira] [Commented] (KAFKA-4899) Fix findbugs warnings in kafka-core

[ https://issues.apache.org/jira/browse/KAFKA-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925336#comment-15925336 ] Colin P. McCabe commented on KAFKA-4899: * {{gradle/findbugs-exclude.xml}}: supress some checks

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Tue, Mar 14, 2017, at 13:36, Becket Qin wrote: > The interface looks good overall. Thanks for the much needed work Colin. Thanks, Becket. > Just a few comments: > > 1. I agree with Gwen that it is a little unfortunate we have to double > the > methods for batching interface. In the new

[jira] [Updated] (KAFKA-4783) Blackbox or pass through converter or ByteArrayConverter for connect

[ https://issues.apache.org/jira/browse/KAFKA-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4783: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[jira] [Commented] (KAFKA-4783) Blackbox or pass through converter or ByteArrayConverter for connect

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

[GitHub] kafka pull request #2599: KAFKA-4783: Add ByteArrayConverter (KIP-128)

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

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Tue, Mar 14, 2017, at 10:15, Ismael Juma wrote: > Hi Gwen, > > I agree with you that it's unfortunate that we now have 4 methods per > operation (including the batch ones). I personally still prefer the > option of using a single class to represent the parameters of each method > (i.e. > 1

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Mon, Mar 13, 2017, at 22:29, Gwen Shapira wrote: > I'm torn between my desire to get this in already and the fact that parts > of the API feel a bit alien to Kafka. > > I will resolve my difficulties by giving my feedback here and then going > to > vote +1 on the vote thread. > Colin can

[GitHub] kafka pull request #2687: KAFKA-4899: Fix findbugs warnings in kafka-core

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2687 KAFKA-4899: Fix findbugs warnings in kafka-core You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4899 Alternatively you can

[jira] [Commented] (KAFKA-4899) Fix findbugs warnings in kafka-core

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

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Ismael, I get your concern that it is more likely for a disk to be slow, or exhibit other forms of non-fatal symptom, after some known fatal error. Then it is weird for user to start broker with the likely-problematic disk in the broker config. In that case, I think there are two things user

Re: [VOTE] KIP-128: Add ByteArrayConverter for Kafka Connect

Great, thanks for voting everyone. This passes with 4 binding and 1 non-binding vote. -Ewen On Wed, Mar 8, 2017 at 12:49 AM, Dongjin Lee wrote: > > > Me too. +1. > > > -- > > > > > Dongjin Lee > > > > > > Software developer in Line+. > > So interested in massive-scale

[jira] [Created] (KAFKA-4899) Fix findbugs warnings in kafka-core

Colin P. McCabe created KAFKA-4899: -- Summary: Fix findbugs warnings in kafka-core Key: KAFKA-4899 URL: https://issues.apache.org/jira/browse/KAFKA-4899 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Ismael, Thanks for the comment. Please see my reply below. On Tue, Mar 14, 2017 at 10:31 AM, Ismael Juma wrote: > Thanks Dong. Comments inline. > > On Fri, Mar 10, 2017 at 6:25 PM, Dong Lin wrote: > > > > I get your point. But I am not sure we

Re: [DISCUSS] KIP-131 : Add access to OffsetStorageReader from SourceConnector

Hi Matthias, Sorry I didn't know this page. Ths KIP has been added to it. Thanks, 2017-03-13 21:30 GMT+01:00 Matthias J. Sax : > Can you please add the KIP to this table: > > https://cwiki.apache.org/confluence/display/KAFKA/ >

[GitHub] kafka pull request #2680: KAFKA-4859: Raised Timeout

Github user original-brownbear closed the pull request at: https://github.com/apache/kafka/pull/2680 --- 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

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

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

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

I'd like to keep the term "Topology" inside the builder class since, as Matthias mentioned, this builder#build() function returns a "Topology" object, whose type is a public class anyways. Although you can argue to let users always call "new KafkaStreams(builder.build())" I think it is still

[GitHub] kafka pull request #1689: HOTFIX: Fix punctuation timestamp in PunctuationQu...

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

[jira] [Commented] (KAFKA-4898) Add timeouts to streams integration tests

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

[GitHub] kafka pull request #2686: KAFKA-4898: Add timeouts to streams integration te...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2686 KAFKA-4898: Add timeouts to streams integration tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4898 Alternatively

[jira] [Created] (KAFKA-4898) Add timeouts to streams integration tests

Colin P. McCabe created KAFKA-4898: -- Summary: Add timeouts to streams integration tests Key: KAFKA-4898 URL: https://issues.apache.org/jira/browse/KAFKA-4898 Project: Kafka Issue Type: Bug

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

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

[GitHub] kafka pull request #2662: KAFKA-4863: Querying window store may return unwan...

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

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

The interface looks good overall. Thanks for the much needed work Colin. Just a few comments: 1. I agree with Gwen that it is a little unfortunate we have to double the methods for batching interface. In the new consumer interface we only have batch interface and it seems to be working fine.

[GitHub] kafka pull request #2685: MINOR: Improve log4j on stream thread and stream p...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2685 MINOR: Improve log4j on stream thread and stream process You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

[jira] [Created] (KAFKA-4897) LogCleaner#cleanSegments should not ignore failures to delete files

Colin P. McCabe created KAFKA-4897: -- Summary: LogCleaner#cleanSegments should not ignore failures to delete files Key: KAFKA-4897 URL: https://issues.apache.org/jira/browse/KAFKA-4897 Project: Kafka

[jira] [Commented] (KAFKA-4896) Offset loading can use more threads

[ https://issues.apache.org/jira/browse/KAFKA-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924764#comment-15924764 ] Onur Karaman commented on KAFKA-4896: - [~junrao] Naively bumping the number of scheduler threads might

[jira] [Commented] (KAFKA-4643) Improve test coverage of StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924713#comment-15924713 ] Matthias J. Sax commented on KAFKA-4643: \cc [~damianguy] > Improve test coverage of

Re: [DISCUSS] KIP-82 - Add Record Headers

Thanks Radai. Great to have a concrete example of the intended usage. Regarding performance, we would need to benchmark, as you said. But there would be a lot of reuse (in essence, we are copying 5 references plus a new object header), so I'd be surprised if that would be the bottleneck compared

Fwd: Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

\cc to dev list Forwarded Message Subject: Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API Date: Tue, 14 Mar 2017 10:43:08 -0700 From: Matthias J. Sax Organization: Confluent Inc To: us...@kafka.apache.org Thanks for your input Michael. >> -

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Thanks Dong. Comments inline. On Fri, Mar 10, 2017 at 6:25 PM, Dong Lin wrote: > > I get your point. But I am not sure we should recommend user to simply > remove disk from the broker config. If user simply does this without > checking the utilization of good disks, replica

[jira] [Commented] (KAFKA-4896) Offset loading can use more threads

[ https://issues.apache.org/jira/browse/KAFKA-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924617#comment-15924617 ] Jun Rao commented on KAFKA-4896: One thing we could probably do is to just set the threads to

[jira] [Created] (KAFKA-4896) Offset loading can use more threads

Jun Rao created KAFKA-4896: -- Summary: Offset loading can use more threads Key: KAFKA-4896 URL: https://issues.apache.org/jira/browse/KAFKA-4896 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Hi Gwen, I agree with you that it's unfortunate that we now have 4 methods per operation (including the batch ones). I personally still prefer the option of using a single class to represent the parameters of each method (i.e. 1 batch and 1 non-batch method per operation). I would follow a very

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

+1 (non-binding) On Tue, Mar 14, 2017 at 8:53 AM, Bill Bejeck wrote: > +1 > > On Tue, Mar 14, 2017 at 11:50 AM, Grant Henke wrote: > > > +1. Agreed. This is a great tool to have. > > > > On Tue, Mar 14, 2017 at 12:33 AM, Gwen Shapira

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

+1 On Tue, Mar 14, 2017 at 8:50 AM, Grant Henke wrote: > +1 > > On Tue, Mar 14, 2017 at 2:44 AM, Sriram Subramanian > wrote: > > > +1 (binding) > > > > Nice work in driving this. > > > > On Mon, Mar 13, 2017 at 10:31 PM, Gwen Shapira

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

+1 On Tue, Mar 14, 2017 at 11:50 AM, Grant Henke wrote: > +1. Agreed. This is a great tool to have. > > On Tue, Mar 14, 2017 at 12:33 AM, Gwen Shapira wrote: > > > +1 (binding) > > > > Nice job - this is going to be super useful. > > > > On Thu, Feb 23,

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

+1 (non-binding) Thanks for the proposal. Regards, --Vahid From: Grant Henke To: dev@kafka.apache.org Date: 03/14/2017 08:51 AM Subject:Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling +1. Agreed. This is a great tool to have. On Tue, Mar

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

+1 On Tue, Mar 14, 2017 at 2:44 AM, Sriram Subramanian wrote: > +1 (binding) > > Nice work in driving this. > > On Mon, Mar 13, 2017 at 10:31 PM, Gwen Shapira wrote: > > > +1 (binding) > > > > I expressed few concerns in the discussion thread, but in

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

+1. Agreed. This is a great tool to have. On Tue, Mar 14, 2017 at 12:33 AM, Gwen Shapira wrote: > +1 (binding) > > Nice job - this is going to be super useful. > > On Thu, Feb 23, 2017 at 4:46 PM, Jorge Esteban Quilcate Otoya < > quilcate.jo...@gmail.com> wrote: > > > Hi All,

[jira] [Commented] (KAFKA-4895) Fix findbugs "format string should use %n rather than \n" in tools

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

[GitHub] kafka pull request #2684: KAFKA-4895: Fix findbugs "format string should use...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2684 KAFKA-4895: Fix findbugs "format string should use %n rather than \n"… … in tools You can merge this pull request into a Git repository by running: $ git pull

[jira] [Assigned] (KAFKA-4895) Fix findbugs "format string should use %n rather than \n" in tools

[ https://issues.apache.org/jira/browse/KAFKA-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-4895: -- Assignee: Colin P. McCabe Component/s: tools > Fix findbugs "format string

[jira] [Updated] (KAFKA-4895) Fix findbugs "format string should use %n rather than \n" in tools

[ https://issues.apache.org/jira/browse/KAFKA-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4895: --- Summary: Fix findbugs "format string should use %n rather than \n" in tools (was: Fix

[jira] [Commented] (KAFKA-4895) Fix findbugs "format string should use %n rather than \n" in tools

[ https://issues.apache.org/jira/browse/KAFKA-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924430#comment-15924430 ] Colin P. McCabe commented on KAFKA-4895: Fix findbugs "format string should use %n rather than \n"

[jira] [Created] (KAFKA-4895) Fix findbugs

Colin P. McCabe created KAFKA-4895: -- Summary: Fix findbugs Key: KAFKA-4895 URL: https://issues.apache.org/jira/browse/KAFKA-4895 Project: Kafka Issue Type: Bug Reporter: Colin

[jira] [Commented] (KAFKA-4894) Fix findbugs "default character set in use" warnings

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

[GitHub] kafka pull request #2683: KAFKA-4894. Fix findbugs "default character set in...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2683 KAFKA-4894. Fix findbugs "default character set in use" warnings You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4894

[jira] [Created] (KAFKA-4894) Fix findbugs "default character set in use" warnings

Colin P. McCabe created KAFKA-4894: -- Summary: Fix findbugs "default character set in use" warnings Key: KAFKA-4894 URL: https://issues.apache.org/jira/browse/KAFKA-4894 Project: Kafka Issue

[jira] [Comment Edited] (KAFKA-4609) KTable/KTable join followed by groupBy and aggregate/count can result in incorrect results

[ https://issues.apache.org/jira/browse/KAFKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924238#comment-15924238 ] Damian Guy edited comment on KAFKA-4609 at 3/14/17 2:07 PM: [~miguno] It is

[jira] [Commented] (KAFKA-4609) KTable/KTable join followed by groupBy and aggregate/count can result in incorrect results

[ https://issues.apache.org/jira/browse/KAFKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924238#comment-15924238 ] Damian Guy commented on KAFKA-4609: --- [~miguno] It is because the caches are flushed independently and

[jira] [Commented] (KAFKA-4609) KTable/KTable join followed by groupBy and aggregate/count can result in incorrect results

[ https://issues.apache.org/jira/browse/KAFKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924093#comment-15924093 ] Michael Noll commented on KAFKA-4609: - Care to elaborate [~damianguy]? Why does this happen only when

[jira] [Updated] (KAFKA-4885) processstreamwithcachedstatestore and other streams benchmarks fail occasionally

[ https://issues.apache.org/jira/browse/KAFKA-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4885: Description: test_id:

[jira] [Updated] (KAFKA-4885) processstreamwithcachedstatestore and other streams benchmarks fail occasionally

[ https://issues.apache.org/jira/browse/KAFKA-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4885: Summary: processstreamwithcachedstatestore and other streams benchmarks fail occasionally (was:

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

I see Jay's point, and I agree with much of it -- notably about being careful which concepts we do and do not expose, depending on which user group / user type is affected. That said, I'm not sure yet whether or not we should get rid of "Topology" (or a similar term) in the DSL. For what it's

[jira] [Resolved] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

[ https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4864. Resolution: Fixed > Kafka Secure Migrator tool doesn't secure all the nodes >

[jira] [Updated] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

[ https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4864: --- Status: Reopened (was: Closed) > Kafka Secure Migrator tool doesn't secure all the nodes >

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

+1 (binding) Nice work in driving this. On Mon, Mar 13, 2017 at 10:31 PM, Gwen Shapira wrote: > +1 (binding) > > I expressed few concerns in the discussion thread, but in general this is > super important to get done. > > On Fri, Mar 10, 2017 at 10:38 AM, Colin McCabe

[jira] [Commented] (KAFKA-4893) async topic deletion conflicts with max topic length

[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923636#comment-15923636 ] Onur Karaman commented on KAFKA-4893: - Maybe the right move is to just add more layers to the log