Re: Simplifying standalone mm2-connect config

Hi Ryanne Thanks for the response. Based on our discussion, raised a jira : KAFKA-9337 . Please find the PR here . On Tue, Dec 24, 2019 at 8:18 PM Ryanne Dolan wrote: > Hello Karan. I agree the initial

Re: MM2 startup delay

Hey, > Do you see any timeouts in the logs? No. At least not exception related to timeout. I see exception like: InstanceAlreadyExistsException, SecurityDisabledException. But I see these issues below, it might be related... Is it expected to see ClassLoader exceptions? [2019-12-27 11:34:48,056]

Re: Kafka 2.4.0 & Mirror Maker 2.0 Error

Hi, I see the same. I just downloaded the Kafka zip and I run: ~/kafka-2.4.0-rc3$ ./bin/connect-mirror-maker.sh config/connect-mirror-maker.properties Peter On Mon, 16 Dec 2019 at 17:14, Ryanne Dolan wrote: > Hey Jamie, are you running the MM2 connectors on an existing Connect > cluster, or w

Re: Mirrormaker 2.0

Hello Ryanne, Are there any plans to implement an easy to use throttling to be a little more kind with the cluster that we start to replicate? I guess it is possible to use the existing throttling in the source and destination clusters, but it is not really easy to use. Also maybe an option to st

Re: Kafka trunk vs master branch

Looks like someone pushed that branch by mistake. We should delete it. Ismael On Thu, Dec 26, 2019, 9:18 PM Matthias J. Sax wrote: > Should we delete `master` ? (Was not even aware it exists...) > > > -Matthias > > On 12/25/19 9:50 AM, M. Manna wrote: > > +1 with what John mentioned. > > > > M

Please help me with link to documentation ... (generics I think)

Hi all of you, I am reading the following code : .. KTable wordCounts = textLines .flatMapValues(textLine -> Arrays.asList(textLine.toLowerCase().split("\\W+"))) .groupBy((key, word) -> word) .count(Materialized.>as("counts-store")); ..

Re: Kafka 2.4.0 & Mirror Maker 2.0 Error

Thanks Peter, I'll take a look. Ryanne On Fri, Dec 27, 2019, 7:48 AM Péter Sinóros-Szabó wrote: > Hi, > > I see the same. > I just downloaded the Kafka zip and I run: > > ~/kafka-2.4.0-rc3$ ./bin/connect-mirror-maker.sh > config/connect-mirror-maker.properties > > Peter > > On Mon, 16 Dec 2019

Significant CPU utilization increase in 2.4.0

I just upgraded one of our test clusters from 2.3.1 to 2.4.0 and the system CPU usage very noticeably increased (from approximately 35% of a CPU to approximately 50% of a CPU). The cluster is very lightly loaded (around 150 messages/sec in aggregate). This CPU time increase is visible symmetrically

Re: MM2 startup delay

Hey Peter. > No Authorizer is configured on the broker You'll need to disable ACL sync to avoid this error. It's harmless tho. > Failed to fetch offsets I have not encountered this. Is it possible one of the clusters is/was unreachable? Are any of the clusters using Kerberos or SSL that may be

Re: Significant CPU utilization increase in 2.4.0

Hi James, Thanks for the report. This is not expected. How many partitions per broker and what Java version? I suggest filing a JIRA and, if possible, attach a flight recorder profile. Ismael On Fri, Dec 27, 2019, 7:07 PM James Brown wrote: > I just upgraded one of our test clusters from 2.3.

Re: Significant CPU utilization increase in 2.4.0

I filed https://issues.apache.org/jira/browse/KAFKA-9339 On Fri, Dec 27, 2019 at 12:24 PM Ismael Juma wrote: > Hi James, > > Thanks for the report. This is not expected. How many partitions per broker > and what Java version? I suggest filing a JIRA and, if possible, attach a > flight recorder p