Re: [VOTE] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

+1 (non-binding) > On Mar 6, 2019, at 3:40 PM, Ryanne Dolan wrote: > > +1 (non-binding) > > Thanks! > Ryanne > > On Wed, Mar 6, 2019, 4:28 PM Konstantine Karantasis < > konstant...@confluent.io> wrote: > >> I'd like to open the vote on KIP-415: Incremental Cooperative Rebalancing >> in Kafka

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

See Changes: [bbejeck] MINOR: improve JavaDocs about global state stores (#6359) -- [...truncated 2.34 MB...] org.apache.kafka.connect.converters.FloatConverterTest > tes

Re: [VOTE] KIP-427: Add AtMinIsr topic partition category (new metric & TopicCommand option)

Thanks for the KIP Kevin. +1 (binding) --Vahid On Wed, Mar 6, 2019 at 8:39 PM Dongjin Lee wrote: > +1 (non-binding) > > On Wed, Mar 6, 2019, 3:14 AM Dong Lin wrote: > > > Hey Kevin, > > > > Thanks for the KIP! > > > > +1 (binding) > > > > Thanks, > > Dong > > > > On Tue, Mar 5, 2019 at 9:38 A

Re: [VOTE] KIP-427: Add AtMinIsr topic partition category (new metric & TopicCommand option)

+1 (non-binding) On Wed, Mar 6, 2019, 3:14 AM Dong Lin wrote: > Hey Kevin, > > Thanks for the KIP! > > +1 (binding) > > Thanks, > Dong > > On Tue, Mar 5, 2019 at 9:38 AM Kevin Lu wrote: > > > Hi All, > > > > I would like to start the vote thread for KIP-427: Add AtMinIsr topic > > partition cat

[jira] [Created] (KAFKA-8059) Flaky Test DynamicConnectionQuotaTest #testDynamicConnectionQuota

Matthias J. Sax created KAFKA-8059: -- Summary: Flaky Test DynamicConnectionQuotaTest #testDynamicConnectionQuota Key: KAFKA-8059 URL: https://issues.apache.org/jira/browse/KAFKA-8059 Project: Kafka

[jira] [Created] (KAFKA-8058) ConnectRestExtensionContext does not return list of connectors from its ConnectClusterState

Chris Egerton created KAFKA-8058: Summary: ConnectRestExtensionContext does not return list of connectors from its ConnectClusterState Key: KAFKA-8058 URL: https://issues.apache.org/jira/browse/KAFKA-8058

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

See

Re: [VOTE] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

+1 (non-binding) Thanks! Ryanne On Wed, Mar 6, 2019, 4:28 PM Konstantine Karantasis < konstant...@confluent.io> wrote: > I'd like to open the vote on KIP-415: Incremental Cooperative Rebalancing > in Kafka Connect > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-415%3A+Incremental+Coo

Build failed in Jenkins: kafka-2.2-jdk8 #46

See Changes: [rajinisivaram] KAFKA-7979 - Clean up threads and increase timeout in PartitionTest [rajinisivaram] KAFKA-8038 - Fix timing issue in SslTransportLayerTest.testCloseSsl ---

[VOTE] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

I'd like to open the vote on KIP-415: Incremental Cooperative Rebalancing in Kafka Connect https://cwiki.apache.org/confluence/display/KAFKA/KIP-415%3A+Incremental+Cooperative+Rebalancing+in+Kafka+Connect a proposal that will allow Kafka Connect to scale significantly the number of connectors and

Re: [DISCUSS] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

After almost two months since this discussion thread on KIP-415 was opened and more than 4 months since the design doc on Incremental Cooperative Rebalancing was posted, I believe that the open items have been discussed and that KIP-415, in its current form, reflects the outcome of our discussions

Re: [VOTE] 2.2.0 RC1

Thanks for testing the RC Jakub! I agree, that both issue are no reason to cancel the current RC. I'll make sure that the doc fixes go into 2.2 webpage when we do the release though. Thanks for the patches! -Matthias On 3/6/19 11:58 AM, Jakub Scholz wrote: > Thanks for driving the release Mat

[jira] [Resolved] (KAFKA-8057) Producer (and probably consumer) retains IP address of broker instead of resolving

[ https://issues.apache.org/jira/browse/KAFKA-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved KAFKA-8057. --- Resolution: Fixed Fix Version/s: 2.1.1 > Producer (and probably consumer) retains IP a

Re: [VOTE] 2.2.0 RC1

Thanks for driving the release Matthias. I noticed two very minor issues while testing the RC1 and opened PRs against master: * https://github.com/apache/kafka/pull/6379 * https://github.com/apache/kafka/pull/6381 I assume it might not be worth including these into 2.2 since it is nothing serious.

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

See Changes: [bbejeck] Moved 'expired-window-' and 'late-' record-drop to StreamsMetricsImpl -- [...truncated 2.33 MB...] org.apache.kafka.streams.processor.internals.Glob

[jira] [Resolved] (KAFKA-8038) Flaky Test SslTransportLayerTest#testCloseSsl

[ https://issues.apache.org/jira/browse/KAFKA-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-8038. --- Resolution: Fixed > Flaky Test SslTransportLayerTest#testCloseSsl > -

[jira] [Resolved] (KAFKA-8006) Guard calls to init() and close() within user code

[ https://issues.apache.org/jira/browse/KAFKA-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-8006. Resolution: Fixed Assignee: Sophie Blee-Goldman Fix Version/s: 2.3.0 > Guar

[jira] [Created] (KAFKA-8056) Replace FindCoordinator request/response with automated protocol

Mickael Maison created KAFKA-8056: - Summary: Replace FindCoordinator request/response with automated protocol Key: KAFKA-8056 URL: https://issues.apache.org/jira/browse/KAFKA-8056 Project: Kafka

[jira] [Created] (KAFKA-8057) Producer (and probably consumer) retains IP address of broker instead of resolving

Bolke de Bruin created KAFKA-8057: - Summary: Producer (and probably consumer) retains IP address of broker instead of resolving Key: KAFKA-8057 URL: https://issues.apache.org/jira/browse/KAFKA-8057 Pr

Jenkins build is back to normal : kafka-2.2-jdk8 #45

See

[jira] [Created] (KAFKA-8055) Flaky Test LogCleanerParameterizedIntegrationTest#cleanerTest

Matthias J. Sax created KAFKA-8055: -- Summary: Flaky Test LogCleanerParameterizedIntegrationTest#cleanerTest Key: KAFKA-8055 URL: https://issues.apache.org/jira/browse/KAFKA-8055 Project: Kafka

[jira] [Created] (KAFKA-8054) KafkaProducer(Properties, Serializer, Serializer) fails when serializers are lambdas

Margaret Figura created KAFKA-8054: -- Summary: KafkaProducer(Properties, Serializer, Serializer) fails when serializers are lambdas Key: KAFKA-8054 URL: https://issues.apache.org/jira/browse/KAFKA-8054

[jira] [Resolved] (KAFKA-7963) Extract hard-coded Streams metric name strings to centralized place

[ https://issues.apache.org/jira/browse/KAFKA-7963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-7963. Resolution: Fixed > Extract hard-coded Streams metric name strings to centralized place > -

[jira] [Created] (KAFKA-8053) kafka-topics.sh gives confusing error message when the topic doesn't exist

Jakub Scholz created KAFKA-8053: --- Summary: kafka-topics.sh gives confusing error message when the topic doesn't exist Key: KAFKA-8053 URL: https://issues.apache.org/jira/browse/KAFKA-8053 Project: Kafka

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Ah yes, I recall it all now. That answers that question as to why I had caching disabled. I can certainly re-enable it since I believe the main concern was simply about reconciling those two iterators. A lack of knowledge there on my part. Thank you John for weighing in - we certainly both do app

[jira] [Created] (KAFKA-8052) Intermittent INVALID_FETCH_SESSION_EPOCH error on FETCH request

Bartek Jakub created KAFKA-8052: --- Summary: Intermittent INVALID_FETCH_SESSION_EPOCH error on FETCH request Key: KAFKA-8052 URL: https://issues.apache.org/jira/browse/KAFKA-8052 Project: Kafka

[jira] [Resolved] (KAFKA-7979) Flaky Test PartitionTest#testDelayedFetchAfterAppendRecords

[ https://issues.apache.org/jira/browse/KAFKA-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7979. --- Resolution: Fixed Reviewer: Ismael Juma > Flaky Test PartitionTest#testDelayedFetchAfte

4 Apache Events in 2019: DC Roadshow soon; next up Chicago, Las Vegas, and Berlin!

Dear Apache Enthusiast, (You’re receiving this because you are subscribed to one or more user mailing lists for an Apache Software Foundation project.) TL;DR: * Apache Roadshow DC is in 3 weeks. Register now at https://apachecon.com/usroadshowdc19/ * Registration for Apache Roadshow Chicago is

[jira] [Resolved] (KAFKA-7976) Flaky Test DynamicBrokerReconfigurationTest#testUncleanLeaderElectionEnable

[ https://issues.apache.org/jira/browse/KAFKA-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7976. --- Resolution: Fixed Reviewer: Manikumar > Flaky Test DynamicBrokerReconfigurationTest#tes

Re: Apache Kafka Memory Leakage???

Hi Syed, no worries, glad I could help! If it helps in any way, I still think that this may just be a case of a misunderstood metric. The documentation for the value from your screenshot is a bit weird. If this is a paid subscription for SnapLogic, it might be worthwhile reaching out to them for

Re: Apache Kafka Memory Leakage???

Sonke, Thanks so much again. As per your suggestion, I created an executable jar file for kafka consumer that runs infinitely. And I have used VisualVM tool to capture the memory stats. Below are the three memory stats I have captured: Stats1: https://i.imgur.com/JfnmNRX.png Stats2: htt

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

See