Upgrading MSK (Kafka) brokers machine type took more than an hour

0

I upgraded 3 brokers in MSK from Kafka.t3.small --> to large. The operation to upgrade took 1 hour 20 minutes which is extremely high. Why should it take that long just to upgrade without running anything at all on those brokers?

Please fix this.

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

Dear Customer,

I understand that the broker instance type upgrade operation took much time. During the upgrade, we take each broker down at a time (which is called as rolling update) and upgrade the instance type and perform health checks at our end on the newly added instance type to make sure it is working fine. Due to this rolling update, one broker goes down at a time and remaining brokers will be available to perform the produce consume operations if you are following the MSK High Availability best practices[1]. However, we are working on this concern to reduce this time as much as possible from our end. Please accept our sincere apologies for the inconvenience caused.

[1] https://docs.aws.amazon.com/msk/latest/developerguide/bestpractices.html#ensure-high-availability

AWS
支援工程師
已回答 8 個月前

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

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

回答問題指南