So it seems that MM2 is doing a lot of small steps to get the offsets and
consumer groups, am I right?
Maybe this need some optimization or batching. Well I am just guessing
here, I don't really know much about how it works.
Do you have any idea maybe it if can be speed up with configuration?
Tha
Hey,
so I turned on debug logging and now I see the MM2 does a lot, so it is
hard to tell exactly what :D
So, what I see the most during that "not mirroring messages" period is logs
about:
- [AdminClient clientId=adminclient-31] Queueing
Call(callName=findCoordinator, deadlineMs=1584976266682) wi
Hmm, maybe turn on debugging info and try to figure out what Connect is
doing during that time.
Ryanne
On Fri, Mar 20, 2020 at 6:15 AM Péter Sinóros-Szabó
wrote:
> Hi,
>
> I don't have the previous logs, so I restarted MM2, that produces the same
> results. So new logs:
>
> MM2 starts and seems
Hi,
I don't have the previous logs, so I restarted MM2, that produces the same
results. So new logs:
MM2 starts and seems to be ready, but not mirroring message:
[2020-03-20 10:50:11,985] INFO [Producer
clientId=connector-producer-MirrorCheckpointConnector-0] Cluster ID:
700ZEsu0ShuzPZ6lZE54_Q (o
Peter, can you share any log lines like "x took y ms" or "x took too long
(y ms)" or "timed out running task x"?
Ryanne
On Tue, Mar 17, 2020 at 10:45 AM Péter Sinóros-Szabó
wrote:
> Hey,
>
> Running a MM2 cluster to mirror from A->B clusters I noticed that when I
> add a new topic to A cluster,
Ah, I'm sorry, this is not the setting you need (it's actually the period
before "Found ... topic-partitions").
Please, ignore my message :)
Ivan
On Tue, 17 Mar 2020 at 18:04, Ivan Yurchenko
wrote:
> Hi,
>
> You need to set refresh.topics.interval.seconds, which is 10 minutes by
> default.
>
>
Hi,
You need to set refresh.topics.interval.seconds, which is 10 minutes by
default.
Ivan
On Tue, 17 Mar 2020 at 17:45, Péter Sinóros-Szabó
wrote:
> Hey,
>
> Running a MM2 cluster to mirror from A->B clusters I noticed that when I
> add a new topic to A cluster, MM2 will notice it:
> [2020-03
Hey,
Running a MM2 cluster to mirror from A->B clusters I noticed that when I
add a new topic to A cluster, MM2 will notice it:
[2020-03-17 13:14:05,477] INFO Found 2719 topic-partitions on main. 1 are
new. 0 were removed. Previously had 2718.
(org.apache.kafka.connect.mirror.MirrorSourceConnector
