Hey,
I did some further debugging on this.
I say that the following happened just before the real huge mirroring
traffic starts:
[2020-01-08 10:48:51,926] INFO Starting with 2294 previously uncommitted
partitions. (org.apache.kafka.connect.mirror.MirrorSourceTask:94)
[2020-01-08 10:48:51,928] IN
Hi Ryanne,
> > 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
misconfigured?
Clusters were reachable and working fine according to our monitoring. It
might be some network issu
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
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]
And can you share the patch...
On Sun, Dec 22, 2019 at 10:34 PM Vishal Santoshi
wrote:
> We also have a large number of topics 1500 plus and in a cross DC
> replication. How do we increase the default timeouts ?
>
>
> On Wed, Dec 11, 2019 at 2:26 PM Ryanne Dolan
> wrote:
>
>> Hey Peter. Do you
We also have a large number of topics 1500 plus and in a cross DC
replication. How do we increase the default timeouts ?
On Wed, Dec 11, 2019 at 2:26 PM Ryanne Dolan wrote:
> Hey Peter. Do you see any timeouts in the logs? The internal scheduler will
> timeout each task after 60 seconds by defa
Hey Peter. Do you see any timeouts in the logs? The internal scheduler will
timeout each task after 60 seconds by default, which might not be long
enough to finish some of the bootstrap tasks in your case. My team has
observed that behavior in super-flaky environments, e.g. when connectivity
drops
Hi,
I am experimenting with Mirror Make 2 in 2.4.0-rc3. It seems to start up
fine, connects to both source and destination, creates new topics...
But it does not start to actually mirror the messages until about 12
minutes after MM2 was started. I would expect it to start mirroring in some
seconds
