MSK Failover and OS Patch

Question

IHAC, the customer experienced a failure due to OS Patch failure while using MSK. Our advice on this is to scale up MSK.
Here, the customer asked additional questions.

1. What is the minimum period of notice (e-mail) for MSK Patch (a week ago?)?
2. Is the problem caused by the number of partitions or is there any other possible case?
3. The customer is using MSK through a triple redundancy configuration(use multi-az with three instance), so was it impossible to avoid failure through this? I am wondering how to respond when OS Path fails or how to set an alarm.

If you have a good guide, please let me know.

Answer

> 1. What is the minimum period of notice (e-mail) for MSK Patch (a week ago?)?

7 days

>2. Is the problem caused by the number of partitions or is there any other possible case?

It depends on the issue you faced. Please elaborate your issue for more understanding.

> 3. The customer is using MSK through a triple redundancy configuration(use multi-az with three instance), so was it impossible to avoid failure through this? I am wondering how to respond when OS Path fails or how to set an alarm.

Make sure that the cluster is following the high availability best practices:
[+] https://docs.aws.amazon.com/msk/latest/developerguide/bestpractices.html#ensure-high-availability

If you still have concerns, please reach out to us over a support case with the issue details and concerned MSK Cluster ARN.

MSK Failover and OS Patch

Relevant content