[
https://issues.apache.org/jira/browse/KAFKA-17784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889719#comment-17889719
]
Greg Harris commented on KAFKA-17784:
-------------------------------------
> However, I have set the broker configuration log.cleanup.policy=delete. Will
> this conflict with the above topic-specific setting?
The topic-specific setting will take precedence.
> Additionally, is there another way to set cleanup.policy=compact without
> using the kafka-configs.sh command, such as configuring it directly in the
> configuration file?
These topics, if created by MirrorMaker, should have the cleanup policy already
set-up. Now that the topics already exist, you will need to manually modify
them like you said.
If this is a new cluster without critical data in the topic, you can also
delete the topics and start over in a clean cluster. Otherwise you've
potentially already lost data due to the delete policy.
You can influence some of the creation parameters using the config file:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-605%3A+Expand+Connect+Worker+Internal+Topic+Settings]
and also change the topic name, if this happens to be a name collision.
> Mirror Maker2 Pod CrashLoopbackOff
> ----------------------------------
>
> Key: KAFKA-17784
> URL: https://issues.apache.org/jira/browse/KAFKA-17784
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
> Affects Versions: 3.7.1
> Reporter: George Yang
> Priority: Blocker
> Attachments: connect-1.log
>
>
> When I use k8s deployment with mirrormaker v3.7.1, and deploy one kafka node
> in each data center, I always got the crashloopbackoff error, please see the
> attachment.
>
> The configuration of mirrormaker is:
> ```configuration
> clusters = idca, idcb
> idca.bootstrap.servers = 192.168.2.146:13399
> idcb.bootstrap.servers = 192.168.2.147:13399
> idca->idcb.enabled = true
> idca->idcb.topics = .*
> idcb->idca.enabled = true
> idcb->idca.topics = .*
> replication.factor=1
> tasks.max=6
> emit.checkpoints.interval.seconds=5
> idca.producer.acks=all
> idca.producer.batch.size=50000
> idca.consumer.auto.offset.reset=latest
> idcb.consumer.auto.offset.reset=latest
> idca.consumer.max.poll.interval.ms=20000
> idcb.consumer.max.poll.interval.ms=20000
> refresh.topics.enabled=true
> refresh.topics.interval.seconds=5
> refresh.groups.enabled=true
> refresh.groups.interval.seconds=5
> dedicated.mode.enable.internal.rest = true
> idca.scheduled.rebalance.max.delay.ms=20000
> idcb.scheduled.rebalance.max.delay.ms=20000
> checkpoints.topic.replication.factor=3
> heartbeats.topic.replication.factor=3
> offset-syncs.topic.replication.factor=3
> offset.storage.replication.factor=3
> status.storage.replication.factor=3
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
