Subject: Running a stand alone Mirror Maker 2.0 cluster and Issues


The above may not be an issue as in  it just uses  the returned class
loader to resolve the Connector I think .  What is not obvious, why it does
not go ahead and consume ..

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,571] INFO refreshing known
target topics took 15 ms (org.apache.kafka.connect.mirror.Scheduler:95)

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,574] INFO Started
MirrorSourceConnector with 120 topic-partitions.
(org.apache.kafka.connect.mirror.MirrorSourceConnector:121)

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,574] INFO Starting
MirrorSourceConnector took 160 ms.
(org.apache.kafka.connect.mirror.MirrorSourceConnector:122)

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,577] INFO Finished creating
connector MirrorSourceConnector
(org.apache.kafka.connect.runtime.Worker:272)

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,578] ERROR Plugin class
loader for connector:
'org.apache.kafka.connect.mirror.MirrorSourceConnector' was not found.
Returning:
org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@2262b621
(org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165)

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,579] INFO
SourceConnectorConfig values:

[mm2-dev-749469cf68-vpm2l] config.action.reload = restart

[mm2-dev-749469cf68-vpm2l] connector.class =
org.apache.kafka.connect.mirror.MirrorSourceConnector

[mm2-dev-749469cf68-vpm2l] errors.log.enable = false

[mm2-dev-749469cf68-vpm2l] errors.log.include.messages = false

[mm2-dev-749469cf68-vpm2l] errors.retry.delay.max.ms = 60000

[mm2-dev-749469cf68-vpm2l] errors.retry.timeout = 0

[mm2-dev-749469cf68-vpm2l] errors.tolerance = none

[mm2-dev-749469cf68-vpm2l] header.converter = null

[mm2-dev-749469cf68-vpm2l] key.converter = null

[mm2-dev-749469cf68-vpm2l] name = MirrorSourceConnector

[mm2-dev-749469cf68-vpm2l] tasks.max = 48

[mm2-dev-749469cf68-vpm2l] transforms = []

[mm2-dev-749469cf68-vpm2l] value.converter = null

[mm2-dev-749469cf68-vpm2l]
(org.apache.kafka.connect.runtime.SourceConnectorConfig:347)

[mm2-dev-749469cf68-vpm2l] [2019-10-24 20:26:07,580] INFO
EnrichedConnectorConfig values:

[mm2-dev-749469cf68-vpm2l] config.action.reload = restart

[mm2-dev-749469cf68-vpm2l] connector.class =
org.apache.kafka.connect.mirror.MirrorSourceConnector

[mm2-dev-749469cf68-vpm2l] errors.log.enable = false

[mm2-dev-749469cf68-vpm2l] errors.log.include.messages = false

[mm2-dev-749469cf68-vpm2l] errors.retry.delay.max.ms = 60000

[mm2-dev-749469cf68-vpm2l] errors.retry.timeout = 0

[mm2-dev-749469cf68-vpm2l] errors.tolerance = none

[mm2-dev-749469cf68-vpm2l] header.converter = null

[mm2-dev-749469cf68-vpm2l] key.converter = null

[mm2-dev-749469cf68-vpm2l] name = MirrorSourceConnector

[mm2-dev-749469cf68-vpm2l] tasks.max = 48

[mm2-dev-749469cf68-vpm2l] transforms = []

[mm2-dev-749469cf68-vpm2l] value.converter = null

[mm2-dev-749469cf68-vpm2l]
(org.apache.kafka.connect.runtime.ConnectorConfig$EnrichedConnectorConfig:347)

And from there on nothing..
On Thu, Oct 24, 2019 at 3:02 PM Vishal Santoshi <[EMAIL PROTECTED]>
wrote: