Select Language:
If your upgrade process seems to be stuck on Amazon MSK, here’s a simple way to understand and fix the issue.
First, you should check the current status of the upgrade. Using the AWS Command Line Interface (CLI), run the command to describe the cluster operation, providing your specific cluster operation ARN. This will tell you what step the upgrade is stuck on, such as INITIALIZE_UPDATE, UPDATE_APACHE_KAFKA_BINARIES, or FINALIZE_UPDATE.
It’s important to know that Amazon MSK doesn’t automatically upgrade Kafka versions. These upgrades are started manually by someone with access to your AWS account. The upgrade you’re seeing was probably initiated by a team member on April 23, 2026.
Since you’re facing a production problem with the upgrade being stuck, the best step is to contact AWS Support. Here’s what to do:
- Open a support case through the AWS Support Center in your AWS Management Console. This is the direct way to get help from AWS engineers.
- Check your support plan. If you have Business, Enterprise On-Ramp, or Enterprise Support, you’ll get a quicker response since these plans prioritize urgent issues.
- When you file the case, include the cluster ARN and the operation ARN. Providing these details helps support engineers troubleshoot more efficiently.
The upgrade process works by rolling out updates across brokers to keep your service available. If the process has been stuck at 50% for more than 48 hours, it indicates a problem that only AWS Support can fix safely. Avoid trying to manually interfere with your cluster while the upgrade is underway, as this could cause more issues.
For more information, you can review the official AWS documentation on Kafka version upgrades and cluster updates:
Upgrade Kafka Version
Update MSK Cluster Configuration
ChatGPT
Perplexity
Gemini AI
Grok AI
