The issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades have been resolved.
Fixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring.
If you are experiencing any issues, please contact support.
No components marked as affected
Resolved
The issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades have been resolved.
Fixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring.
If you are experiencing any issues, please contact support.
Monitoring
We have deployed fixes for the issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades, and migrations have been re-enabled.
We are continuing to monitor the situation to ensure services remain stable.
If you are experiencing any issues, please contact support.
Identified
We have identified issues affecting KRaft migrations (Kafka 3.8 to 3.9 upgrades). We have paused all migrations while we work on a fix. If you are experiencing any issues, please contact support.
Identified
We have identified two separate problems:
An issue in migration code
An upstream bug
We are working on the fix for the migration issue and back-porting the fix for the upstream bug.
If you have any issues, please contact support.
Investigating
We have paused Kafka 3.8 ->3.9 upgrades as we are investigating an issue with KRaft migration during the upgrade.
Aiven is actively monitoring affected services and applying mitigations where required.
Impact: Existing Kafka services continue to run. Customers attempting to upgrade Kafka services from version 3.8 to 3.9 will not be able to complete the upgrade while KRaft migrations are paused.
Next update: We will provide an update once more information is available.
