Hello,
I am trying to run MirrorMaker 2.0 on kafka version 3.0.0 on my source
cluster and my target kafka cluster is in kafka version 2.7.2.
I am facing issues with topic configuration to create topics on my target
cluster.
[2021-12-14 12:28:33,071] WARN [MirrorSourceConnector|worker] Could not
Hello,
I agree with time taken for consumer initialization processes
But actually in the test I am taking care of that and I am waiting for the
consumer to be initiated and only then starting the producer to discount
the initialization delay.
So, are there any more processes happening during the
Hi Christian,
You can check this answer by Colin (Kafka PMC member):
https://lists.apache.org/thread/r53hykwsb621rj37m5w1l1c7l71s6qc6
In short, it might need 6 month or a year.
Thank you.
Luke
On Wed, Dec 15, 2021 at 2:30 AM Christian A. Mathiesen
wrote:
> Hi,
>
> In the quickstart guide on
I'll second that. Thank you!
Brian
Quoting Luke Chen :
Hi Jun,
It looks great and clear!
Thank you for working on the public statement!
Thank you.
Luke
On Wed, Dec 15, 2021 at 8:34 AM Jun Rao wrote:
Hi, Everyone,
Just to provide an update. https://kafka.apache.org/cve-list is now
Hi Jun,
It looks great and clear!
Thank you for working on the public statement!
Thank you.
Luke
On Wed, Dec 15, 2021 at 8:34 AM Jun Rao wrote:
> Hi, Everyone,
>
> Just to provide an update. https://kafka.apache.org/cve-list is now
> updated
> with this CVE.
>
> Thanks,
>
> Jun
>
> On Tue,
Hi, Everyone,
Just to provide an update. https://kafka.apache.org/cve-list is now updated
with this CVE.
Thanks,
Jun
On Tue, Dec 14, 2021 at 3:30 PM Jun Rao wrote:
> Hi, Israel,
>
> Randall added some clarification for the connectors in the PR.
>
> Thanks,
>
> Jun
>
> On Tue, Dec 14, 2021 at
Hi, Israel,
Randall added some clarification for the connectors in the PR.
Thanks,
Jun
On Tue, Dec 14, 2021 at 12:10 PM Israel Ekpo wrote:
> Do we want to add a disclaimer that users need to check their connectors to
> see if it uses log4j2?
>
> Though the core library does not use this
Do we want to add a disclaimer that users need to check their connectors to
see if it uses log4j2?
Though the core library does not use this dependency, it is possible
external connectors that use it could introduce vulnerabilities if they
depend on the affected log4j2 version
On Tue, Dec 14,
Sure I will take a look at it shortly
On Tue, Dec 14, 2021 at 12:44 PM Jun Rao wrote:
> Hi, Luke,
>
> Thanks for the analysis. We are trying to put a public statement on this
> through this PR: https://github.com/apache/kafka-site/pull/388. If anyone
> has more feedback, we can iterate on the
Hi,
In the quickstart guide on the Kafka website, the following is stated:
«Note: Soon, ZooKeeper will no longer be required by Apache Kafka»
According to release notes, «early access of replace ZooKeeper with a
self-managed quorum» was added April 19 2021.
The question is; when will this
Hi, Luke,
Thanks for the analysis. We are trying to put a public statement on this
through this PR: https://github.com/apache/kafka-site/pull/388. If anyone
has more feedback, we can iterate on the PR.
Thanks,
Jun
On Tue, Dec 14, 2021 at 7:53 AM Murilo Tavares wrote:
> What about
What about Kafka-Connect?
Anyone has checked if any of the Confluent KafkaConnect docker images embed
log4j v2?
Thanks
On Mon, 13 Dec 2021 at 21:39, Luke Chen wrote:
> Hi all,
>
> Here's the comments for CVE-2021-44228 vulnerability *from SLF4J project*.
> REF: http://slf4j.org/log4shell.html
>
confirm
13 matches
Mail list logo
