Questions
4 of 5
Basics
Cluster Architecture
Topics, Partitions and Records
Producers
Consumers
Consumer Groups
Offset Management
Replication and Fault Tolerance
Storage Internals
Networking and Request Processing
Performance and Throughput
Delivery Semantics
Transactions
Kafka Streams
Kafka Connect
Schema and Serialization
Security
Error Handling and Retry Patterns
Ordering and Partitioning Design
Testing
Monitoring and Observability
Debugging and Troubleshooting
Deployment and Operations
Admin and CLI Operations
Reliability and Disaster Recovery
Integration Patterns
Modern Kafka Architecture
Advanced Internals
Scalability and Capacity Planning
Architecture and System Design
Production Best Practices
Expert Edge Cases
Versioning and Upgrades
Admin and CLI Operations
Senior End-to-End Scenarios
Difficulty: 8/10
Safe operations, Reassignment throttling, Production SLO protection
Executing large partition reassignments safely
I treat a large reassignment as a capacity-managed migration. Before moving data, I estimate replica bytes, validate destination capacity and rack placement, check ISR health, and capture a baseline for broker and client performance. I divide the work into bounded batches, begin with a canary batch, and adjust the movement rate against production SLOs. The goal is not merely to finish quickly; it is to finish without unacceptable client latency or loss of replica safety.
javascript
- 1
Preflight broker and rack health, destination disk headroom, network capacity, replica sizes, ISR health, and client SLO baselines.
- 2
Stage by broker and replica volume, not merely by topic count; a few very large partitions can dominate load.
- 3
Start with a canary batch and monitor replication throughput, under-replicated partitions, ISR shrinkage, disk latency, network saturation, request latency, and consumer lag.
- 4
Use throttling controls supported by the installed version and adjust the rate based on measured impact. Avoid overlapping maintenance tasks without estimating combined load.
- 5
Define stop conditions before starting, such as sustained SLO violations, growing under-replication, destination disk pressure, or repeated ISR loss.
- 6
Track each batch's plan, owner, status, verification result, and next action. Aggressive movement finishes sooner but raises contention; conservative movement protects clients but takes longer.
- 7
Common mistake: watching only reassignment progress. A move can progress while client traffic degrades or replication safety falls.
Scenario Questions
0-2 years experience
2-5 years experience
5-8 years experience
8+ years experience
- 1You must move several terabytes while maintaining producer-latency SLOs. How would you size batches and adjust throughput? How would you automate and govern this process?
- 2A migration breaches latency and ISR thresholds halfway through. How would you pause, preserve state, communicate, and resume safely? How would you recover safely from a partial failure?