Re: Security vulnerabilities in kafka:2.13-2.6.0/2.7.0 docker image

[Luke Chen]

Hi Ashish,
I suggested that you upgrade to V2.8.
I checked 2 of the CVEs, and are fixed (or not used, like libfetch) in
V2.8.
If you still found the CVEs existed in V2.8, please raise it.

Thank you.
Luke




On Wed, Sep 1, 2021 at 4:07 AM Ashish Patil  wrote:

> Hi Team
>
> I wanted to use the 2.6.0 docker image for Kafka but It has lots of
> security vulnerabilities.
> Please find the below list of security vulnerabilities
> **
> CVE-2021-36159
> CVE-2020-25649 
> CVE-2021-22926
> CVE-2021-22922
> CVE-2021-22924
> CVE-2021-22922
> CVE-2021-22924
> CVE-2021-31535
> CVE-2019-17571 
> **
>
> I did raise this issue here
> https://github.com/wurstmeister/kafka-docker/issues/681 but it looks like
> the issue is within the Kafka binary.
>
> Do we have any plan to fix this in the coming version or any suggestions
> around this?
>
> Thanks
>
> Ashish
>

Re: [DISCUSS] KIP-771: KRaft broker should not expose controller metrics

[Colin McCabe]

Hi Ryan,

Thanks for the KIP.

Hmm, we don't really use the term "zookeeper brokers." That is confusing since 
ZK and Kafka are separate services. I would suggest a term like pre-KRaft 
brokers.

> Zookeeper brokers currently register 0 for every controller metric.

It's not 0 for every broker, is it? We should outline the circumstances when 
it's not 0 (i.e. one of these brokers is the active controller).

> KRaft does not have this issue because processes with the "broker" role are 
> never
> elected as the active controller. 

This is somewhat misleading since a node could have bother controller and 
broker roles. Maybe a clearer way of writing this would be "nodes that are not 
eligible to become controllers."

> Proposed Changes
> Zookeeper brokers expose 0 for controller metrics. KRaft brokers should not.

It seems like we should document what metrics standby controllers expose when 
in KRaft mode. It seems like the two options are exposing 0 for these metrics, 
or exposing a similar value to the active controller.

best,
Colin


On Fri, Aug 27, 2021, at 14:30, Ron Dagostino wrote:
> Thanks for the KIP, Ryan.  I agree this makes sense.  It also reflects the
> state of affairs right now: KRaft nodes that do not have the controller
> role currently do not expose these metrics.  Assuming this KIP ends up
> being accepted, we would then close KAFKA-13140 and its associated PR
> https://github.com/apache/kafka/pull/11133.
> 
> Ron
> 
> On Fri, Aug 27, 2021 at 5:19 PM Ryan Dielhenn
>  wrote:
> 
> > Hello kafka devs,
> >
> > I would like to start a discussion on a KIP I have created to change how
> > controller metrics are exposed for KRaft brokers.
> >
> > Here is the KIP:
> >
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP+771%3A+KRaft+brokers+should+not+expose+controller+metrics
> >
> > Regards,
> > Ryan Dielhenn
> >
> 

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #441

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 489290 lines...]
[2021-08-31T20:44:39.064Z] PlaintextConsumerTest > 
testLowMaxFetchSizeForRequestAndPartition() PASSED
[2021-08-31T20:44:39.064Z] 
[2021-08-31T20:44:39.064Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnStopPolling() STARTED
[2021-08-31T20:44:59.036Z] 
[2021-08-31T20:44:59.036Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnStopPolling() PASSED
[2021-08-31T20:44:59.036Z] 
[2021-08-31T20:44:59.036Z] PlaintextConsumerTest > 
testMaxPollIntervalMsDelayInRevocation() STARTED
[2021-08-31T20:45:03.207Z] 
[2021-08-31T20:45:03.207Z] PlaintextConsumerTest > 
testMaxPollIntervalMsDelayInRevocation() PASSED
[2021-08-31T20:45:03.207Z] 
[2021-08-31T20:45:03.207Z] PlaintextConsumerTest > 
testPerPartitionLagMetricsCleanUpWithAssign() STARTED
[2021-08-31T20:45:09.121Z] 
[2021-08-31T20:45:09.121Z] PlaintextConsumerTest > 
testPerPartitionLagMetricsCleanUpWithAssign() PASSED
[2021-08-31T20:45:09.121Z] 
[2021-08-31T20:45:09.121Z] PlaintextConsumerTest > 
testPartitionsForInvalidTopic() STARTED
[2021-08-31T20:45:11.903Z] 
[2021-08-31T20:45:11.903Z] PlaintextConsumerTest > 
testPartitionsForInvalidTopic() PASSED
[2021-08-31T20:45:11.903Z] 
[2021-08-31T20:45:11.903Z] PlaintextConsumerTest > 
testPauseStateNotPreservedByRebalance() STARTED
[2021-08-31T20:45:18.599Z] 
[2021-08-31T20:45:18.599Z] PlaintextConsumerTest > 
testPauseStateNotPreservedByRebalance() PASSED
[2021-08-31T20:45:18.599Z] 
[2021-08-31T20:45:18.599Z] PlaintextConsumerTest > 
testFetchHonoursFetchSizeIfLargeRecordNotFirst() STARTED
[2021-08-31T20:45:23.184Z] 
[2021-08-31T20:45:23.184Z] PlaintextConsumerTest > 
testFetchHonoursFetchSizeIfLargeRecordNotFirst() PASSED
[2021-08-31T20:45:23.184Z] 
[2021-08-31T20:45:23.184Z] PlaintextConsumerTest > testSeek() STARTED
[2021-08-31T20:45:33.189Z] 
[2021-08-31T20:45:33.189Z] PlaintextConsumerTest > testSeek() PASSED
[2021-08-31T20:45:33.189Z] 
[2021-08-31T20:45:33.189Z] PlaintextConsumerTest > 
testConsumingWithNullGroupId() STARTED
[2021-08-31T20:45:46.244Z] 
[2021-08-31T20:45:46.244Z] PlaintextConsumerTest > 
testConsumingWithNullGroupId() PASSED
[2021-08-31T20:45:46.244Z] 
[2021-08-31T20:45:46.244Z] PlaintextConsumerTest > testPositionAndCommit() 
STARTED
[2021-08-31T20:45:50.854Z] 
[2021-08-31T20:45:50.854Z] PlaintextConsumerTest > testPositionAndCommit() 
PASSED
[2021-08-31T20:45:50.854Z] 
[2021-08-31T20:45:50.854Z] PlaintextConsumerTest > 
testFetchRecordLargerThanMaxPartitionFetchBytes() STARTED
[2021-08-31T20:45:56.139Z] 
[2021-08-31T20:45:56.139Z] PlaintextConsumerTest > 
testFetchRecordLargerThanMaxPartitionFetchBytes() PASSED
[2021-08-31T20:45:56.139Z] 
[2021-08-31T20:45:56.139Z] PlaintextConsumerTest > testUnsubscribeTopic() 
STARTED
[2021-08-31T20:46:00.679Z] 
[2021-08-31T20:46:00.679Z] PlaintextConsumerTest > testUnsubscribeTopic() PASSED
[2021-08-31T20:46:00.679Z] 
[2021-08-31T20:46:00.679Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnClose() STARTED
[2021-08-31T20:46:12.004Z] 
[2021-08-31T20:46:12.004Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnClose() PASSED
[2021-08-31T20:46:12.004Z] 
[2021-08-31T20:46:12.004Z] PlaintextConsumerTest > 
testMultiConsumerStickyAssignor() STARTED
[2021-08-31T20:46:25.161Z] 
[2021-08-31T20:46:25.161Z] PlaintextConsumerTest > 
testMultiConsumerStickyAssignor() PASSED
[2021-08-31T20:46:25.161Z] 
[2021-08-31T20:46:25.161Z] PlaintextConsumerTest > 
testFetchRecordLargerThanFetchMaxBytes() STARTED
[2021-08-31T20:46:29.700Z] 
[2021-08-31T20:46:29.700Z] PlaintextConsumerTest > 
testFetchRecordLargerThanFetchMaxBytes() PASSED
[2021-08-31T20:46:29.700Z] 
[2021-08-31T20:46:29.700Z] PlaintextConsumerTest > testAutoCommitOnClose() 
STARTED
[2021-08-31T20:46:33.911Z] 
[2021-08-31T20:46:33.911Z] PlaintextConsumerTest > testAutoCommitOnClose() 
PASSED
[2021-08-31T20:46:33.911Z] 
[2021-08-31T20:46:33.911Z] PlaintextConsumerTest > testListTopics() STARTED
[2021-08-31T20:46:37.976Z] 
[2021-08-31T20:46:37.976Z] PlaintextConsumerTest > testListTopics() PASSED
[2021-08-31T20:46:37.976Z] 
[2021-08-31T20:46:37.976Z] PlaintextConsumerTest > 
testExpandingTopicSubscriptions() STARTED
[2021-08-31T20:46:43.279Z] 
[2021-08-31T20:46:43.279Z] PlaintextConsumerTest > 
testExpandingTopicSubscriptions() PASSED
[2021-08-31T20:46:43.279Z] 
[2021-08-31T20:46:43.279Z] PlaintextConsumerTest > 
testMultiConsumerDefaultAssignor() STARTED
[2021-08-31T20:46:57.587Z] 
[2021-08-31T20:46:57.587Z] PlaintextConsumerTest > 
testMultiConsumerDefaultAssignor() PASSED
[2021-08-31T20:46:57.587Z] 
[2021-08-31T20:46:57.587Z] PlaintextConsumerTest > testInterceptors() STARTED
[2021-08-31T20:47:02.783Z] 
[2021-08-31T20:47:02.783Z] PlaintextConsumerTest > testInterceptors() PASSED
[2021-08-31T20:47:02.783Z] 
[2021-08-31T20:47:02.783Z] PlaintextConsumerTest > 
testConsumingWithEmptyGroupId() STARTED

Security vulnerabilities in kafka:2.13-2.6.0/2.7.0 docker image

[Ashish Patil]

Hi Team

I wanted to use the 2.6.0 docker image for Kafka but It has lots of security 
vulnerabilities.
Please find the below list of security vulnerabilities
**
CVE-2021-36159
CVE-2020-25649
CVE-2021-22926
CVE-2021-22922
CVE-2021-22924
CVE-2021-22922
CVE-2021-22924
CVE-2021-31535
CVE-2019-17571
**

I did raise this issue here 
https://github.com/wurstmeister/kafka-docker/issues/681 but it looks like the 
issue is within the Kafka binary.

[cid:image001.png@01D79EAB.B342BA90]

Do we have any plan to fix this in the coming version or any suggestions around 
this?
Thanks
Ashish

Re: [VOTE] KIP-761: Add Total Blocked Time Metric to Streams

[Guozhang Wang]

Thanks for letting us know, Rohan.

On Tue, Aug 31, 2021 at 1:08 AM Rohan Desai  wrote:

> FYI I've updated the metric names in the KIP to the form ".*-time-ns-total"
> and clarified that the times being measured are in nanoseconds.
>
> On Wed, Jul 21, 2021 at 5:09 PM Rohan Desai 
> wrote:
>
> > Now that the discussion thread's been open for a few days, I'm calling
> for
> > a vote on
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-761%3A+Add+Total+Blocked+Time+Metric+to+Streams
> >
>


-- 
-- Guozhang

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #122

[Apache Jenkins Server]

See 

Re: [VOTE] 3.0.0 RC1

[Konstantine Karantasis]

Small correction to my previous email.
The actual link for public preview of the 3.0.0 blog post draft is:

https://blogs.apache.org/preview/kafka/?previewEntry=what-s-new-in-apache6

(see also the email thread with title: [DISCUSS] Please review the 3.0.0
blog post)

Best,
Konstantine

On Tue, Aug 31, 2021 at 6:34 PM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

>
> Hello Kafka users, developers and client-developers,
>
> This is the second release candidate for Apache Kafka 3.0.0.
> It corresponds to a major release that includes many new features,
> including:
>
> * The deprecation of support for Java 8 and Scala 2.12.
> * Kafka Raft support for snapshots of the metadata topic and
> other improvements in the self-managed quorum.
> * Deprecation of message formats v0 and v1.
> * Stronger delivery guarantees for the Kafka producer enabled by default.
> * Optimizations in OffsetFetch and FindCoordinator requests.
> * More flexible Mirror Maker 2 configuration and deprecation of
> Mirror Maker 1.
> * Ability to restart a connector's tasks on a single call in Kafka Connect.
> * Connector log contexts and connector client overrides are now enabled
> by default.
> * Enhanced semantics for timestamp synchronization in Kafka Streams.
> * Revamped public API for Stream's TaskId.
> * Default serde becomes null in Kafka Streams and several
> other configuration changes.
>
> You may read and review a more detailed list of changes in the 3.0.0 blog
> post draft here:
>
> https://blogs.apache.org/roller-ui/authoring/preview/kafka/?previewEntry=what-s-new-in-apache6
>
> Release notes for the 3.0.0 release:
> https://home.apache.org/~kkarantasis/kafka-3.0.0-rc1/RELEASE_NOTES.html
>
> *** Please download, test and vote by Wednesday, September 8, 2021 ***
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> https://kafka.apache.org/KEYS
>
> * Release artifacts to be voted upon (source and binary):
> https://home.apache.org/~kkarantasis/kafka-3.0.0-rc1/
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> https://home.apache.org/~kkarantasis/kafka-3.0.0-rc1/javadoc/
>
> * Tag to be voted upon (off 3.0 branch) is the 3.0.0 tag:
> https://github.com/apache/kafka/releases/tag/3.0.0-rc1
>
> * Documentation:
> https://kafka.apache.org/30/documentation.html
>
> * Protocol:
> https://kafka.apache.org/30/protocol.html
>
> * Successful Jenkins builds for the 3.0 branch:
> Unit/integration tests:
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/3.0/121/pipeline/
> (only few flaky failures)
> System tests:
> https://jenkins.confluent.io/job/system-test-kafka/job/3.0/57/
>
> /**
>
> Thanks,
> Konstantine
>

[DISCUSS] Please review the 3.0.0 blog post

[Konstantine Karantasis]

With the opportunity of the latest release candidate (RC1) I have also
published a draft of the 3.0.0 release announcement, available for public
preview, here:

https://blogs.apache.org/preview/kafka/?previewEntry=what-s-new-in-apache6

This blog post is scheduled to be published in
https://blogs.apache.org/kafka/ soon after the release candidate gets
approved and 3.0.0 gets promoted to production.

With that in mind, I would greatly appreciate your reviews, ideally by
Wednesday, September 8, 2021, which is also the current target date to
download, test and vote for the current 3.0.0 release candidate.

Sincerely,
Konstantine

[jira] [Resolved] (KAFKA-13205) Clarify API specification of Kafka Connect endpoint

[Jonathan Kaleve (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Kaleve resolved KAFKA-13205.
-
Resolution: Fixed

Resolution see https://github.com/strimzi/strimzi-kafka-operator/issues/5427

> Clarify API specification of Kafka Connect endpoint
> ---
>
> Key: KAFKA-13205
> URL: https://issues.apache.org/jira/browse/KAFKA-13205
> Project: Kafka
>  Issue Type: Improvement
>  Components: KafkaConnect
>Affects Versions: 2.7.0
>Reporter: Jonathan Kaleve
>Priority: Major
>
> Since Version 2.5, Kafka Connect exposes an Endpoint for getting all topics 
> related to a Connector via its REST API (see [the original 
> KIP|https://cwiki.apache.org/confluence/display/KAFKA/KIP-558%3A+Track+the+set+of+actively+used+topics+by+connectors+in+Kafka+Connect]).
> While the original KIP proposed the Response Payload to look as follows: 
> {code:java}
> {
>   "some-source": {
> "topics": [
>   "foo",
>   "bar",
>   "baz",   
> ]
>   }
> }
> {code}
> The documentation by Confluent states the same: 
> [https://docs.confluent.io/platform/current/connect/references/restapi.html#get--connectors-(string-name)-topics]
> The [actual 
> Code|https://github.com/apache/kafka/blob/2.7/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/resources/ConnectorsResource.java#L198],
>  however, produces a result of the following form:
> {code:java}
> {
>   "some-source": {
> "connector": "some-source",
> "topics": [
>   "foo",
>   "bar",
>   "baz",   
> ]
>   }
> }
> {code}
>  
>  This poses a problem to some Applications (like [Strimzi 
> Operator|https://github.com/strimzi/strimzi-kafka-operator]) since they 
> expect the response to be of type {{Map>>}} 
> (see 
> [here|https://github.com/strimzi/strimzi-kafka-operator/blob/61a2301390fb9ecc87feb1925d0c2d2f1b2f8107/cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/assembly/KafkaConnectApiImpl.java#L610]),
>  but in Kafka Connect, the return type is actually {{Map Object>>}} (see [this 
> test|https://github.com/apache/kafka/blob/2.7/connect/runtime/src/test/java/org/apache/kafka/connect/runtime/rest/resources/ConnectorsResourceTest.java#L884],
>  for example)
>  Which type should be expected here? Is the endpoint intended to return the 
> type documented by Confluent, or the type that is actually present in the 
> code? 
> Also: I might be overlooking something, but it seems there is no official 
> documentation of the specific API endpoints of Kafka Connect. Is that correct?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[VOTE] 3.0.0 RC1

[Konstantine Karantasis]

Hello Kafka users, developers and client-developers,

This is the second release candidate for Apache Kafka 3.0.0.
It corresponds to a major release that includes many new features,
including:

* The deprecation of support for Java 8 and Scala 2.12.
* Kafka Raft support for snapshots of the metadata topic and
other improvements in the self-managed quorum.
* Deprecation of message formats v0 and v1.
* Stronger delivery guarantees for the Kafka producer enabled by default.
* Optimizations in OffsetFetch and FindCoordinator requests.
* More flexible Mirror Maker 2 configuration and deprecation of
Mirror Maker 1.
* Ability to restart a connector's tasks on a single call in Kafka Connect.
* Connector log contexts and connector client overrides are now enabled
by default.
* Enhanced semantics for timestamp synchronization in Kafka Streams.
* Revamped public API for Stream's TaskId.
* Default serde becomes null in Kafka Streams and several
other configuration changes.

You may read and review a more detailed list of changes in the 3.0.0 blog
post draft here:
https://blogs.apache.org/roller-ui/authoring/preview/kafka/?previewEntry=what-s-new-in-apache6

Release notes for the 3.0.0 release:
https://home.apache.org/~kkarantasis/kafka-3.0.0-rc1/RELEASE_NOTES.html

*** Please download, test and vote by Wednesday, September 8, 2021 ***

Kafka's KEYS file containing PGP keys we use to sign the release:
https://kafka.apache.org/KEYS

* Release artifacts to be voted upon (source and binary):
https://home.apache.org/~kkarantasis/kafka-3.0.0-rc1/

* Maven artifacts to be voted upon:
https://repository.apache.org/content/groups/staging/org/apache/kafka/

* Javadoc:
https://home.apache.org/~kkarantasis/kafka-3.0.0-rc1/javadoc/

* Tag to be voted upon (off 3.0 branch) is the 3.0.0 tag:
https://github.com/apache/kafka/releases/tag/3.0.0-rc1

* Documentation:
https://kafka.apache.org/30/documentation.html

* Protocol:
https://kafka.apache.org/30/protocol.html

* Successful Jenkins builds for the 3.0 branch:
Unit/integration tests:
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/3.0/121/pipeline/
(only few flaky failures)
System tests: https://jenkins.confluent.io/job/system-test-kafka/job/3.0/57/

/**

Thanks,
Konstantine

Re: [VOTE] 3.0.0 RC0

[Konstantine Karantasis]

There were a few issues during the staging of maven artifacts in the nexus
staging repository for RC0.

Closing the vote early here in favor of RC1 that has been staged
successfully and will be announced shortly.

Thanks,
Konstantine


On Fri, Aug 27, 2021 at 7:10 AM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the first candidate for release of Apache Kafka 3.0.0.
> It is a major release that includes many new features, including:
>
> * The deprecation of support for Java 8 and Scala 2.12.
> * Kafka Raft support for snapshots of the metadata topic and other
> improvements in the self-managed quorum.
> * Deprecation of message formats v0 and v1.
> * Stronger delivery guarantees for the Kafka producer enabled by default.
> * Optimizations in OffsetFetch and FindCoordinator requests.
> * More flexible Mirror Maker 2 configuration and deprecation of Mirror
> Maker 1.
> * Ability to restart a connector's tasks on a single call in Kafka Connect.
> * Connector log contexts and connector client overrides are now enabled by
> default.
> * Enhanced semantics for timestamp synchronization in Kafka Streams.
> * Revamped public API for Stream's TaskId.
> * Default serde becomes null in Kafka Streams and several other
> configuration changes.
>
> Release notes for the 3.0.0 release:
> https://home.apache.org/~kkarantasis/kafka-3.0.0-rc0/RELEASE_NOTES.html
>
> *** Please download, test and vote by Friday, September 3, 2021 ***
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> https://kafka.apache.org/KEYS
>
> * Release artifacts to be voted upon (source and binary):
> https://home.apache.org/~kkarantasis/kafka-3.0.0-rc0/
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> https://home.apache.org/~kkarantasis/kafka-3.0.0-rc0/javadoc/
>
> * Tag to be voted upon (off 3.0 branch) is the 3.0.0 tag:
> https://github.com/apache/kafka/releases/tag/3.0.0-rc0
>
> * Documentation:
> https://kafka.apache.org/30/documentation.html
>
> * Protocol:
> https://kafka.apache.org/30/protocol.html
>
> * Successful Jenkins builds for the 3.0 branch:
> Unit/integration tests:
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/3.0/118/pipeline/
> System tests:
> https://jenkins.confluent.io/job/system-test-kafka/job/3.0/53/
>
> /**
>
> Thanks,
> Konstantine
>

[jira] [Created] (KAFKA-13256) Possible NPE in ConfigDef when rendering (enriched) RST or HTML when documentation is not set/NULL

[Jira]

René Kerner created KAFKA-13256:
---

 Summary: Possible NPE in ConfigDef when rendering (enriched) RST 
or HTML when documentation is not set/NULL
 Key: KAFKA-13256
 URL: https://issues.apache.org/jira/browse/KAFKA-13256
 Project: Kafka
  Issue Type: Bug
  Components: clients
Affects Versions: 2.8.0
Reporter: René Kerner


While working on Debezium I discovered the following issue:

When Kafka's ConfigDef renders the HTML or RST documentation representation of 
the config definition, it requires `documentation` member variable to be a 
java.lang.String instance that's set to an actual value different than NULL, 
else NPE happens:

{code}
 b.append(key.documentation.replaceAll("\n", ""));
{code}

{code}
 for (String docLine : key.documentation.split("\n")) {
{code}

 

When `documentation` is not set/NULL I suggest to either set a valid String 
like "No documentation available" or skip that config key.

 

I could provide a PR to fix this soon.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 2.8 #74

[Apache Jenkins Server]

See 

Re: [VOTE] KIP-761: Add Total Blocked Time Metric to Streams

[Rohan Desai]

FYI I've updated the metric names in the KIP to the form ".*-time-ns-total"
and clarified that the times being measured are in nanoseconds.

On Wed, Jul 21, 2021 at 5:09 PM Rohan Desai  wrote:

> Now that the discussion thread's been open for a few days, I'm calling for
> a vote on
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-761%3A+Add+Total+Blocked+Time+Metric+to+Streams
>

[jira] [Created] (KAFKA-13255) Mirrormaker config property config.properties.exclude is not working as expected

[Anamika Nadkarni (Jira)]

Anamika Nadkarni created KAFKA-13255:


 Summary: Mirrormaker config property config.properties.exclude is 
not working as expected 
 Key: KAFKA-13255
 URL: https://issues.apache.org/jira/browse/KAFKA-13255
 Project: Kafka
  Issue Type: Bug
  Components: mirrormaker
Affects Versions: 2.8.0
Reporter: Anamika Nadkarni


Objective - Use MM2 (kafka connect in distributed cluster) for data migration 
between cluster hosted in private data center and aws msk cluster.

Steps performed -
 # Started kafka-connect service.
 # Created 3 MM2 connectors (i.e. source connector, checkpoint connector and 
heartbeat connector). Curl commands used to create connectors are in the 
attached file.  To exclude certain config properties while topic replication, 
we are using the 'config.properties.exclude' property in the MM2 source 
connector.

Expected -

Source topic 'dev.portlandDc.anamika.helloMsk' should be successfully created 
in destination cluster.

Actual -

Creation of the source topic 'dev.portlandDc.anamika.helloMsk' in destination 
cluster fails with an error. Error is
{code:java}
[2021-08-06 06:13:40,944] WARN [mm2-msc|worker] Could not create topic 
dev.portlandDc.anamika.helloMsk. 
(org.apache.kafka.connect.mirror.MirrorSourceConnector:371)
org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic 
config name: confluent.value.schema.validation{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)