Build failed in Jenkins: kafka-2.3-jdk8 #42

See Changes: [jason] KAFKA-8386; Use COORDINATOR_NOT_AVAILABLE error when group is Dead -- [...truncated 2.92 MB...] kafka.zk.KafkaZkClientTest > testLogDirGetters PASSED kaf

[jira] [Created] (KAFKA-8497) kafka streams application占用内存很高

sunqing created KAFKA-8497: -- Summary: kafka streams application占用内存很高 Key: KAFKA-8497 URL: https://issues.apache.org/jira/browse/KAFKA-8497 Project: Kafka Issue Type: Bug Components: strea

Re: Newbie on lookout for work

Thanks a bunch for the reply and I’ll make sure to check it out On Thu, Jun 6, 2019 at 4:43 AM Gwen Shapira wrote: > Hi, > > You can look at our contribution guidelines: > https://kafka.apache.org/contributing > > We have a number of open "newbie" tickets in JIRA, perhaps one of them > will be i

Jenkins build is back to normal : kafka-trunk-jdk11 #605

See

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

See Changes: [jason] KAFKA-8386; Use COORDINATOR_NOT_AVAILABLE error when group is Dead [github] KAFKA-8400; Do not update follower replica state if the log read failed -

Re: [VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

Thanks Viktor, proposed metrics are really useful to monitor replication status on brokers. +1 (non-binding) On Thu, Jun 6, 2019 at 2:05 AM Colin McCabe wrote: > +1 (binding) > > best, > Colin > > > On Wed, Jun 5, 2019, at 03:38, Viktor Somogyi-Vass wrote: > > Hi Folks, > > > > This vote sunk a

[jira] [Created] (KAFKA-8496) Add system test for compatibility and upgrade path (part 6)

Guozhang Wang created KAFKA-8496: Summary: Add system test for compatibility and upgrade path (part 6) Key: KAFKA-8496 URL: https://issues.apache.org/jira/browse/KAFKA-8496 Project: Kafka Is

[jira] [Created] (KAFKA-8495) Make Round-robin / RangeAssignor to be "sticky" (part 5)

Guozhang Wang created KAFKA-8495: Summary: Make Round-robin / RangeAssignor to be "sticky" (part 5) Key: KAFKA-8495 URL: https://issues.apache.org/jira/browse/KAFKA-8495 Project: Kafka Issue

[jira] [Created] (KAFKA-8494) Refactor Consumer#StickyAssignor to support incremental protocol (part 4)

Guozhang Wang created KAFKA-8494: Summary: Refactor Consumer#StickyAssignor to support incremental protocol (part 4) Key: KAFKA-8494 URL: https://issues.apache.org/jira/browse/KAFKA-8494 Project: Kafk

[jira] [Created] (KAFKA-8493) Add PartitionsLost API in RebalanceListener

Guozhang Wang created KAFKA-8493: Summary: Add PartitionsLost API in RebalanceListener Key: KAFKA-8493 URL: https://issues.apache.org/jira/browse/KAFKA-8493 Project: Kafka Issue Type: Sub-tas

[jira] [Created] (KAFKA-8492) Modify ConsumerCoordinator Algorithm with incremental protocol (part 2)

Guozhang Wang created KAFKA-8492: Summary: Modify ConsumerCoordinator Algorithm with incremental protocol (part 2) Key: KAFKA-8492 URL: https://issues.apache.org/jira/browse/KAFKA-8492 Project: Kafka

[jira] [Created] (KAFKA-8491) Bump up Consumer Protocol to v2 (part 1)

Guozhang Wang created KAFKA-8491: Summary: Bump up Consumer Protocol to v2 (part 1) Key: KAFKA-8491 URL: https://issues.apache.org/jira/browse/KAFKA-8491 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-8490) Use `Migrated` and `Deleted` state to replace consumer group `Dead` state

Boyang Chen created KAFKA-8490: -- Summary: Use `Migrated` and `Deleted` state to replace consumer group `Dead` state Key: KAFKA-8490 URL: https://issues.apache.org/jira/browse/KAFKA-8490 Project: Kafka

[jira] [Created] (KAFKA-8489) Remove group immediately when DeleteGroup request could be completed

Boyang Chen created KAFKA-8489: -- Summary: Remove group immediately when DeleteGroup request could be completed Key: KAFKA-8489 URL: https://issues.apache.org/jira/browse/KAFKA-8489 Project: Kafka

Re: [DISCUSS] KIP-471: Expose RocksDB Metrics in Kafka Streams

I think Bruno's 2) is that for a segmented store, the access rate on different segments will very likely be different. And in fact, most of the access should be on the "latest" segment unless 1) very late arrived data, which should be captured on the higher-level `lateness` metrics already, and 2)

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Hi Vito, sorry for dropping this discussion on the floor a while back. I was just re-reading the KIP and discussion thread, and I think it is shaping out nicely! I like the overall hierarchy of the exception classes. Some things are still not 100% clear: You listed all methods that may throw a

Build failed in Jenkins: kafka-trunk-jdk11 #604

See Changes: [jason] KAFKA-8305; Support default partitions & replication factor in [jason] KAFKA-8386; Use COORDINATOR_NOT_AVAILABLE error when group is Dead -- [...trun

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

See Changes: [jason] KAFKA-8305; Support default partitions & replication factor in -- [...truncated 2.50 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shoul

Re: [VOTE] KIP-475: New Metric to Measure Number of Tasks on a Connector

Thanks, Cyrus. +1 (binding) Randall Hauch On Wed, Jun 5, 2019 at 10:36 AM Andrew Schofield wrote: > +1 (non-binding) > > Andrew Schofield > > On 05/06/2019, 14:04, "Ryanne Dolan" wrote: > > +1 (non-binding) > > Thanks > Ryanne > > On Tue, Jun 4, 2019, 11:29 PM Cyrus Vafadari

Build failed in Jenkins: kafka-2.3-jdk8 #41

See -- [...truncated 2.10 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowIfInMemoryBuiltInStoreIsAccessedWithUntypedMethod[Eos enabled = false] PASSED org.apache.kafka

Re: Newbie on lookout for work

Hi, You can look at our contribution guidelines: https://kafka.apache.org/contributing We have a number of open "newbie" tickets in JIRA, perhaps one of them will be interesting to you: https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20%3D%20Open%20AND%20labels%20i

[jira] [Resolved] (KAFKA-8386) Use COORDINATOR_NOT_AVAILABLE to replace UNKNOWN_MEMBER_ID when the group is not available

[ https://issues.apache.org/jira/browse/KAFKA-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8386. Resolution: Fixed Fix Version/s: 2.3.0 > Use COORDINATOR_NOT_AVAILABLE to replace UN

[jira] [Resolved] (KAFKA-8400) Do not update follower replica state if the log read failed

[ https://issues.apache.org/jira/browse/KAFKA-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8400. Resolution: Fixed Fix Version/s: 2.4.0 > Do not update follower replica state if the

[jira] [Resolved] (KAFKA-8305) AdminClient should support creating topics with default partitions and replication factor

[ https://issues.apache.org/jira/browse/KAFKA-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8305. Resolution: Fixed Assignee: Almog Gavra Fix Version/s: 2.4.0 > AdminClient

Re: [kafka-clients] [VOTE] 2.3.0 RC1

If we get in KAFKA-8487, we may as well do KAFKA-8386 since it causes a similar problem. The patch is ready to be merged. -Jason On Wed, Jun 5, 2019 at 1:29 PM Guozhang Wang wrote: > Hello Colin, > > I caught an issue which would affect KIP-345 ( > https://issues.apache.org/jira/browse/KAFKA-84

[jira] [Resolved] (KAFKA-8433) Give the opportunity to use serializers and deserializers with IntegrationTestUtils

[ https://issues.apache.org/jira/browse/KAFKA-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony C resolved KAFKA-8433. -- Resolution: Won't Fix > Give the opportunity to use serializers and deserializers with > IntegrationTe

Re: [VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

+1 (binding) best, Colin On Wed, Jun 5, 2019, at 03:38, Viktor Somogyi-Vass wrote: > Hi Folks, > > This vote sunk a bit, I'd like to draw some attention to this again in the > hope I get some feedback or votes. > > Thanks, > Viktor > > On Tue, May 7, 2019 at 4:28 PM Harsha wrote: > > > Than

Re: [kafka-clients] [VOTE] 2.3.0 RC1

Hello Colin, I caught an issue which would affect KIP-345 ( https://issues.apache.org/jira/browse/KAFKA-8487) and hence may need to be considered a blocker for this release. Guozhang On Tue, Jun 4, 2019 at 11:31 PM Colin McCabe wrote: > On Tue, Jun 4, 2019, at 23:17, Colin McCabe wrote: > > H

[jira] [Resolved] (KAFKA-8486) How to commit offset via Kafka

[ https://issues.apache.org/jira/browse/KAFKA-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-8486. Resolution: Invalid > How to commit offset via Kafka > --- > >

[jira] [Created] (KAFKA-8488) FetchSessionHandler logging create 73 mb allocation in TLAB which could be no op

Wenshuai Hou created KAFKA-8488: --- Summary: FetchSessionHandler logging create 73 mb allocation in TLAB which could be no op Key: KAFKA-8488 URL: https://issues.apache.org/jira/browse/KAFKA-8488 Project

[jira] [Resolved] (KAFKA-8265) Connect Client Config Override policy

[ https://issues.apache.org/jira/browse/KAFKA-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-8265. Resolution: Fixed Fix Version/s: 2.3 > Connect Client Config Override policy > -

Newbie on lookout for work

Hi All, I'm a newbie for FOSS and I'd like to start contributing to Apache Kafka. Any pointers for beginning would be appreciated. -- *Witharane, D.R.H.* R&D Engineer Synopsys Inc, Colombo 08 Mobile : *+94 7 <%2B94%2071%201127241>7 6746781* Skype : dulvin.rivindu Facebook

[jira] [Resolved] (KAFKA-3816) Provide more context in Kafka Connect log messages using MDC

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-3816. Resolution: Fixed > Provide more context in Kafka Connect log messages using MDC >

[jira] [Created] (KAFKA-8487) Consumer should not resetGeneration upon REBALANCE_IN_PROGRESS in commit response handler

Guozhang Wang created KAFKA-8487: Summary: Consumer should not resetGeneration upon REBALANCE_IN_PROGRESS in commit response handler Key: KAFKA-8487 URL: https://issues.apache.org/jira/browse/KAFKA-8487

Re: [VOTE] KIP-475: New Metric to Measure Number of Tasks on a Connector

+1 (non-binding) Andrew Schofield On 05/06/2019, 14:04, "Ryanne Dolan" wrote: +1 (non-binding) Thanks Ryanne On Tue, Jun 4, 2019, 11:29 PM Cyrus Vafadari wrote: > Hi all, > > Like like to start voting in the following KIP: > > https://nam01.

Re: [VOTE] KIP-475: New Metric to Measure Number of Tasks on a Connector

+1 (non-binding) Thanks Ryanne On Tue, Jun 4, 2019, 11:29 PM Cyrus Vafadari wrote: > Hi all, > > Like like to start voting in the following KIP: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-475%3A+New+Metric+to+Measure+Number+of+Tasks+on+a+Connector > > Discussion thread: > > https

Re: kafka connect stops consuming data when kafka broker goes down

It’s not totally clear, but this may be https://issues.apache.org/jira/plugins/servlet/mobile#issue/KAFKA-7941 For which there is a fix that is very nearly approved: https://github.com/apache/kafka/pull/6283 Paul > On Jun 5, 2019, at 1:26 AM, Srinivas, Kaushik (Nokia - IN/Bangalore) > wrote:

Re: [VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

Hi Folks, This vote sunk a bit, I'd like to draw some attention to this again in the hope I get some feedback or votes. Thanks, Viktor On Tue, May 7, 2019 at 4:28 PM Harsha wrote: > Thanks for the kip. LGTM +1. > > -Harsha > > On Mon, Apr 29, 2019, at 8:14 AM, Viktor Somogyi-Vass wrote: > > Hi

Re: [ANNOUNCE] Apache Kafka 2.2.1

Thanks to all the contributors whose changes are part of this release and thank you Vahid for driving the release :) On Tue, Jun 4, 2019 at 8:03 PM Rajini Sivaram wrote: > Thanks for managing the release, Vahid! > > Regards, > > Rajini > > On Tue, Jun 4, 2019 at 4:45 PM Viktor Somogyi-Vass < > v

[jira] [Created] (KAFKA-8486) How to commit offset via Kafka

Stanislav created KAFKA-8486: - Summary: How to commit offset via Kafka Key: KAFKA-8486 URL: https://issues.apache.org/jira/browse/KAFKA-8486 Project: Kafka Issue Type: Wish Components

Build failed in Jenkins: kafka-2.3-jdk8 #40

See Changes: [cmccabe] MINOR: Update docs to say 2.3 (#6881) -- [...truncated 2.82 MB...] kafka.log.ProducerStateManagerTest > testPrepareUpdateDoesNotMutate PASSED kafka.log