[jira] [Updated] (KAFKA-15505) MM2 consumer group subscription different on target cluster
[
https://issues.apache.org/jira/browse/KAFKA-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Boga updated KAFKA-15505:
--
Description:
I am running mirrormaker2 in distributed mode with 3 nodes and 10 tasks each ,
kafka version: 3.5.1
On the source cluster , i see the consumer group has subscriptions of topic-A
and topic-B, but on the target cluster i am seeing only the subscription of
topic-A
restarting did not help, Also the the consumed offsets of the topic-A are
different on the target cluster, i see the lag of zero for all partitions on
source cluster, but the lag keeps building up on the target cluster
{code:java}
sync.group.offsets.enabled = true
sync.group.offsets.interval.seconds = 1{code}
Any help on this would be appreciated
Thanks,
-srini
was:
I am running mirrormaker2 in distributed mode with 3 nodes and 10 tasks each ,
kafka version: 3.5.1
On the source cluster , i see the consumer group has subscriptions of topic-A
and topic-B, but on the target cluster i am seeing only the subscription of
topic-A
restarting did not help, Also the the consumed offsets of the topic-A are
different on the target cluster, i see the lag of zero for all partitions on
source cluster, but the lag keeps building up on the target cluster
Any help on this would be appreciated
Thanks,
-srini
> MM2 consumer group subscription different on target cluster
> ---
>
> Key: KAFKA-15505
> URL: https://issues.apache.org/jira/browse/KAFKA-15505
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
>Reporter: Srinivas Boga
>Priority: Major
>
> I am running mirrormaker2 in distributed mode with 3 nodes and 10 tasks each
> , kafka version: 3.5.1
> On the source cluster , i see the consumer group has subscriptions of topic-A
> and topic-B, but on the target cluster i am seeing only the subscription of
> topic-A
> restarting did not help, Also the the consumed offsets of the topic-A are
> different on the target cluster, i see the lag of zero for all partitions on
> source cluster, but the lag keeps building up on the target cluster
> {code:java}
> sync.group.offsets.enabled = true
> sync.group.offsets.interval.seconds = 1{code}
>
> Any help on this would be appreciated
>
> Thanks,
> -srini
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (KAFKA-15505) MM2 consumer group subscription different on target cluster
Srinivas Boga created KAFKA-15505: - Summary: MM2 consumer group subscription different on target cluster Key: KAFKA-15505 URL: https://issues.apache.org/jira/browse/KAFKA-15505 Project: Kafka Issue Type: Bug Components: mirrormaker Reporter: Srinivas Boga I am running mirrormaker2 in distributed mode with 3 nodes and 10 tasks each , kafka version: 3.5.1 On the source cluster , i see the consumer group has subscriptions of topic-A and topic-B, but on the target cluster i am seeing only the subscription of topic-A restarting did not help, Also the the consumed offsets of the topic-A are different on the target cluster, i see the lag of zero for all partitions on source cluster, but the lag keeps building up on the target cluster Any help on this would be appreciated Thanks, -srini -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-14898) [ MirrorMaker ] sync.topic.configs.enabled not working as expected
[
https://issues.apache.org/jira/browse/KAFKA-14898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711551#comment-17711551
]
Srinivas Boga commented on KAFKA-14898:
---
[~gharris1727] Thanks for your help on this
Yes i could see that log message which you pointed out, i was running
mirrormaker in distributed mode having 3 nodes and 10 tasks on each
I have verified by running only on one node and it is working as expected
Thanks,
-srini
> [ MirrorMaker ] sync.topic.configs.enabled not working as expected
> --
>
> Key: KAFKA-14898
> URL: https://issues.apache.org/jira/browse/KAFKA-14898
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
>Affects Versions: 3.4.0
>Reporter: Srinivas Boga
>Priority: Major
> Labels: mirrormaker
>
> Hello,
> In my replication set up , i do not want to sync the topic configs, the use
> case is to have different retention time for the topic on the target cluster,
> I am passing the config
> {code:java}
> sync.topic.configs.enabled = false{code}
> but this is not working as expected the topic retention time is being set to
> whatever is being set in the source cluster, looking at the mirrormaker logs
> i can see that MirrorSourceConnector is still setting the above config as true
> {code:java}
> [2023-04-12 17:04:55,184] INFO [MirrorSourceConnector|task-8] ConsumerConfig
> values:
> allow.auto.create.topics = true
> auto.commit.interval.ms = 5000
> auto.include.jmx.reporter = true
> auto.offset.reset = earliest
> bootstrap.servers = [sourcecluster.com:9092]
> check.crcs = true
> client.dns.lookup = use_all_dns_ips
> client.id = consumer-null-2
> client.rack =
> connections.max.idle.ms = 54
> default.api.timeout.ms = 6
> enable.auto.commit = false
> exclude.internal.topics = true
> fetch.max.bytes = 52428800
> fetch.max.wait.ms = 500
> fetch.min.bytes = 1
> group.id = null
> group.instance.id = null
> heartbeat.interval.ms = 3000
> interceptor.classes = []
> internal.leave.group.on.close = true
> internal.throw.on.fetch.stable.offset.unsupported = false
> isolation.level = read_uncommitted
> key.deserializer = class
> org.apache.kafka.common.serialization.ByteArrayDeserializer
> max.partition.fetch.bytes = 1048576
> max.poll.interval.ms = 30
> max.poll.records = 500
> metadata.max.age.ms = 30
> metric.reporters = []
> metrics.num.samples = 2
> metrics.recording.level = INFO
> metrics.sample.window.ms = 3
> partition.assignment.strategy = [class
> org.apache.kafka.clients.consumer.RangeAssignor, class
> org.apache.kafka.clients.consumer.CooperativeStickyAssignor]
> receive.buffer.bytes = 65536
> reconnect.backoff.max.ms = 1000
> reconnect.backoff.ms = 50
> request.timeout.ms = 3
> retry.backoff.ms = 100
> sasl.client.callback.handler.class = null
> sasl.jaas.config = null
> sasl.kerberos.kinit.cmd = /usr/bin/kinit
> sasl.kerberos.min.time.before.relogin = 6
> sasl.kerberos.service.name = null
> sasl.kerberos.ticket.renew.jitter = 0.05
> sasl.kerberos.ticket.renew.window.factor = 0.8
> sasl.login.callback.handler.class = null
> sasl.login.class = null
> sasl.login.connect.timeout.ms = null
> sasl.login.read.timeout.ms = null
> sasl.login.refresh.buffer.seconds = 300
> sasl.login.refresh.min.period.seconds = 60
> sasl.login.refresh.window.factor = 0.8
> sasl.login.refresh.window.jitter = 0.05
> sasl.login.retry.backoff.max.ms = 1
> sasl.login.retry.backoff.ms = 100
> sasl.mechanism = GSSAPI
> sasl.oauthbearer.clock.skew.seconds = 30
> sasl.oauthbearer.expected.audience = null
> sasl.oauthbearer.expected.issuer = null
> sasl.oauthbearer.jwks.endpoint.refresh.ms = 360
> sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms = 1
> sasl.oauthbearer.jwks.endpoint.retry.backoff.ms = 100
> sasl.oauthbearer.jwks.endpoint.url = null
> sasl.oauthbearer.scope.claim.name = scope
> sasl.oauthbearer.sub.claim.name = sub
> sasl.oauthbearer.token.endpoint.url = null
> security.protocol = PLAINTEXT
> security.providers = null
> send.buffer.bytes = 131072
> session.timeout.ms = 45000
> socket.connection.setup.timeout.max.ms = 3
> socket.connection.setup.timeout.ms = 1
> ssl.cipher.suites = null
>
[jira] [Created] (KAFKA-14898) [ MirrorMaker ] sync.topic.configs.enabled not working as expected
Srinivas Boga created KAFKA-14898:
-
Summary: [ MirrorMaker ] sync.topic.configs.enabled not working as
expected
Key: KAFKA-14898
URL: https://issues.apache.org/jira/browse/KAFKA-14898
Project: Kafka
Issue Type: Bug
Components: mirrormaker
Affects Versions: 3.4.0
Reporter: Srinivas Boga
Hello,
In my replication set up , i do not want to sync the topic configs, the use
case is to have different retention time for the topic on the target cluster, I
am passing the config
{code:java}
sync.topic.configs.enabled = false{code}
but this is not working as expected the topic retention time is being set to
whatever is being set in the source cluster, looking at the mirrormaker logs i
can see that MirrorSourceConnector is still setting the above config as true
{code:java}
[2023-04-12 17:04:55,184] INFO [MirrorSourceConnector|task-8] ConsumerConfig
values:
allow.auto.create.topics = true
auto.commit.interval.ms = 5000
auto.include.jmx.reporter = true
auto.offset.reset = earliest
bootstrap.servers = [sourcecluster.com:9092]
check.crcs = true
client.dns.lookup = use_all_dns_ips
client.id = consumer-null-2
client.rack =
connections.max.idle.ms = 54
default.api.timeout.ms = 6
enable.auto.commit = false
exclude.internal.topics = true
fetch.max.bytes = 52428800
fetch.max.wait.ms = 500
fetch.min.bytes = 1
group.id = null
group.instance.id = null
heartbeat.interval.ms = 3000
interceptor.classes = []
internal.leave.group.on.close = true
internal.throw.on.fetch.stable.offset.unsupported = false
isolation.level = read_uncommitted
key.deserializer = class
org.apache.kafka.common.serialization.ByteArrayDeserializer
max.partition.fetch.bytes = 1048576
max.poll.interval.ms = 30
max.poll.records = 500
metadata.max.age.ms = 30
metric.reporters = []
metrics.num.samples = 2
metrics.recording.level = INFO
metrics.sample.window.ms = 3
partition.assignment.strategy = [class
org.apache.kafka.clients.consumer.RangeAssignor, class
org.apache.kafka.clients.consumer.CooperativeStickyAssignor]
receive.buffer.bytes = 65536
reconnect.backoff.max.ms = 1000
reconnect.backoff.ms = 50
request.timeout.ms = 3
retry.backoff.ms = 100
sasl.client.callback.handler.class = null
sasl.jaas.config = null
sasl.kerberos.kinit.cmd = /usr/bin/kinit
sasl.kerberos.min.time.before.relogin = 6
sasl.kerberos.service.name = null
sasl.kerberos.ticket.renew.jitter = 0.05
sasl.kerberos.ticket.renew.window.factor = 0.8
sasl.login.callback.handler.class = null
sasl.login.class = null
sasl.login.connect.timeout.ms = null
sasl.login.read.timeout.ms = null
sasl.login.refresh.buffer.seconds = 300
sasl.login.refresh.min.period.seconds = 60
sasl.login.refresh.window.factor = 0.8
sasl.login.refresh.window.jitter = 0.05
sasl.login.retry.backoff.max.ms = 1
sasl.login.retry.backoff.ms = 100
sasl.mechanism = GSSAPI
sasl.oauthbearer.clock.skew.seconds = 30
sasl.oauthbearer.expected.audience = null
sasl.oauthbearer.expected.issuer = null
sasl.oauthbearer.jwks.endpoint.refresh.ms = 360
sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms = 1
sasl.oauthbearer.jwks.endpoint.retry.backoff.ms = 100
sasl.oauthbearer.jwks.endpoint.url = null
sasl.oauthbearer.scope.claim.name = scope
sasl.oauthbearer.sub.claim.name = sub
sasl.oauthbearer.token.endpoint.url = null
security.protocol = PLAINTEXT
security.providers = null
send.buffer.bytes = 131072
session.timeout.ms = 45000
socket.connection.setup.timeout.max.ms = 3
socket.connection.setup.timeout.ms = 1
ssl.cipher.suites = null
ssl.enabled.protocols = [TLSv1.2]
ssl.endpoint.identification.algorithm = https
ssl.engine.factory.class = null
ssl.key.password = null
ssl.keymanager.algorithm = SunX509
ssl.keystore.certificate.chain = null
ssl.keystore.key = null
ssl.keystore.location = null
ssl.keystore.password = null
ssl.keystore.type = JKS
ssl.protocol = TLSv1.2
ssl.provider = null
ssl.secure.random.implementation = null
sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms = 1
sasl.oauthbearer.jwks.endpoint.retry.backoff.ms = 100
sasl.oauthbearer.jwks.endpoint.url = null
sasl.oauthbearer.scope.claim.name = scope
sasl.oauthbearer.sub.claim.name =
[jira] [Commented] (KAFKA-9827) MM2 doesnt replicate data
[
https://issues.apache.org/jira/browse/KAFKA-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077051#comment-17077051
]
Srinivas Boga commented on KAFKA-9827:
--
Also how can i avoid the suffix(alias) in the topic name, i am in the process
of moving from kafak-0.11 to kafka-2.4.0 and want to setup the replication
either ways till we complete the migration, so that different services can
publish and consume from both the clusters
Thanks,
-srini
> MM2 doesnt replicate data
> -
>
> Key: KAFKA-9827
> URL: https://issues.apache.org/jira/browse/KAFKA-9827
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Dmitry
>Priority: Major
> Attachments: mm2.log
>
>
> I have 2 servers with different node count:
> # 2.4.0 version, 3 nodes, broker port plaintext:9090
> # 2.4.0 version, 1 nodes, broker port plaintext:
> I want to transfer data from cluster 1 -> cluster 2 by mirror maker 2.
> MM2 configuration:
>
> {code:java}
> name = mm2-backupFlow
> topics = .*
> groups = .*
> # specify any number of cluster aliases
> clusters = m1-source, m1-backup
> # connection information for each cluster
> m1-source.bootstrap.servers = 172.17.165.49:9090, 172.17.165.50:9090,
> 172.17.165.51:9090
> m1-backup.bootstrap.servers = 172.17.165.52:
> # enable and configure individual replication flows
> m1-source->m1-backup.enabled = true
> m1-soruce->m1-backup.emit.heartbeats.enabled = false
> {code}
>
> When i start MM2 on each clusters created 3 topics:
> * heartbeat
> * *.internal
> And thats all. Nothing to happend.
> I watching next ERROR's:
> {code:java}
> [2020-04-07 07:19:16,821] ERROR Plugin class loader for connector:
> 'org.apache.kafka.connect.mirror.MirrorHeartbeatConnector' was not found.
> Returning:
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@1e5f4170
> (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165)
> {code}
> {code:java}
> [2020-04-07 07:19:18,312] ERROR Plugin class loader for connector:
> 'org.apache.kafka.connect.mirror.MirrorCheckpointConnector' was not found.
> Returning:
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@1e5f4170
> (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165)
> {code}
> {code:java}
> [2020-04-07 07:19:16,807] ERROR Plugin class loader for connector:
> 'org.apache.kafka.connect.mirror.MirrorSourceConnector' was not found.
> Returning:
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@1e5f4170
> (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165){code}
> Full log in attach
> What i missed ? Help please
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-9827) MM2 doesnt replicate data
[
https://issues.apache.org/jira/browse/KAFKA-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077012#comment-17077012
]
Srinivas Boga commented on KAFKA-9827:
--
Im also facing exact same issue, this is the config i am using
mm2.properties
clusters: stg-240,prod-011
stg-240.bootstrap.servers = stg-240:9092
prod-011.bootstrap.servers = prod-011:9092
stg-240->prod-011.enabled = true
stg-240->prod-011.topics = test
prod-011->stg-240.enabled = true
prod-011->stg-240.topics = test
{code:java}
{code}
> MM2 doesnt replicate data
> -
>
> Key: KAFKA-9827
> URL: https://issues.apache.org/jira/browse/KAFKA-9827
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Dmitry
>Priority: Major
> Attachments: mm2.log
>
>
> I have 2 servers with different node count:
> # 2.4.0 version, 3 nodes, broker port plaintext:9090
> # 2.4.0 version, 1 nodes, broker port plaintext:
> I want to transfer data from cluster 1 -> cluster 2 by mirror maker 2.
> MM2 configuration:
>
> {code:java}
> name = mm2-backupFlow
> topics = .*
> groups = .*
> # specify any number of cluster aliases
> clusters = m1-source, m1-backup
> # connection information for each cluster
> m1-source.bootstrap.servers = 172.17.165.49:9090, 172.17.165.50:9090,
> 172.17.165.51:9090
> m1-backup.bootstrap.servers = 172.17.165.52:
> # enable and configure individual replication flows
> m1-source->m1-backup.enabled = true
> m1-soruce->m1-backup.emit.heartbeats.enabled = false
> {code}
>
> When i start MM2 on each clusters created 3 topics:
> * heartbeat
> * *.internal
> And thats all. Nothing to happend.
> I watching next ERROR's:
> {code:java}
> [2020-04-07 07:19:16,821] ERROR Plugin class loader for connector:
> 'org.apache.kafka.connect.mirror.MirrorHeartbeatConnector' was not found.
> Returning:
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@1e5f4170
> (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165)
> {code}
> {code:java}
> [2020-04-07 07:19:18,312] ERROR Plugin class loader for connector:
> 'org.apache.kafka.connect.mirror.MirrorCheckpointConnector' was not found.
> Returning:
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@1e5f4170
> (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165)
> {code}
> {code:java}
> [2020-04-07 07:19:16,807] ERROR Plugin class loader for connector:
> 'org.apache.kafka.connect.mirror.MirrorSourceConnector' was not found.
> Returning:
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@1e5f4170
> (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:165){code}
> Full log in attach
> What i missed ? Help please
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
