Bird
0
0

MirrorMaker 2 replication lags behind. Which misconfiguration might cause this?

medium📝 Debug Q7 of 15
Kafka - Multi-Datacenter and Replication
MirrorMaker 2 replication lags behind. Which misconfiguration might cause this?
AUsing 'target.cluster.bootstrap.servers' for source cluster
BLow 'tasks.max' value limiting parallelism
CSetting 'sync.topic.acls.enabled' to false
DEnabling 'emit.heartbeats.enabled'
Step-by-Step Solution
Solution:

  1. Step 1: Understand 'tasks.max' impact

    'tasks.max' controls how many parallel tasks run; a low value can slow replication causing lag.

  2. Step 2: Evaluate other options

    ACL sync false doesn't cause lag, misusing target cluster config causes connection failure, heartbeats do not slow replication.

  3. Final Answer:

    Low 'tasks.max' value limiting parallelism -> Option B

  4. Quick Check:

    Low tasks.max = replication lag [OK]
Quick Trick: Increase 'tasks.max' to reduce lag [OK]
Common Mistakes:
MISTAKES
  • Ignoring parallelism limits
  • Confusing ACL sync with performance
  • Misconfiguring cluster bootstrap servers

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Advanced Stream Processing - Error handling in streams - Quiz 4medium Advanced Stream Processing - Why advanced patterns handle complex flows - Quiz 10hard Event-Driven Architecture - Why event-driven scales applications - Quiz 1easy Event-Driven Architecture - Dead letter queue pattern - Quiz 11easy Event-Driven Architecture - CQRS pattern - Quiz 3easy Kubernetes and Cloud Deployment - Why cloud-native deployment matters - Quiz 5medium Kubernetes and Cloud Deployment - Amazon MSK - Quiz 9hard Performance Tuning - Consumer throughput optimization - Quiz 12easy Security - Security best practices - Quiz 13medium Security - SSL/TLS encryption - Quiz 6medium