Error: kafka.common.AdminCommandFailedException: The reassignment failed due to an unexpected error.

0

We often balance our partitions across brokers when there is an imbalance. We occasionally encounter "NO_REASSIGNMENT_IN_PROGRESS" errors in addition to reassignment directly failing at the beginning. Any insights into what can we do better to avoid these?

已提問 1 年前檢視次數 287 次
1 個回答
1

Hi,

The "NO_REASSIGNMENT_IN_PROGRESS" is a result that you may get when there's no reassignment currently in progress for the specified partitions, which might be the case if a previous reassignment completed or failed, or if no reassignment was initiated.

The error message "The reassignment failed due to an unexpected error" is a more generic message and it indicates that something went wrong during the reassignment operation, but doesn't provide specific details about the cause. There are several potential reasons for this error, including issues with the broker, replication factor issues, issues with the ZooKeeper, and so on.

Here are couple of things you could consider:

  1. Ensure healthy cluster state: Before doing reassignment, ensure your MSK cluster is in a healthy state. All brokers should be up and running, and underreplicated partitions should ideally be zero.

  2. Validate your reassignment JSON: Make sure the JSON file used for partition reassignment is correct and can be parsed successfully. The tool does not validate if the reassignment maintains the replication factor or not, so ensure this is manually validated.

If none of the above helps, it might be useful to provide more details. In that case, please create a support case with us, using the following link:

https://console.aws.amazon.com/support/home#/case/create

AWS
支援工程師
已回答 1 年前
AWS
專家
已審閱 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南