Does Updating an Active MSK cause data loss

Thanks for the answer. The update was completed but partition counts didn't increase when I ran this command ./kafka-topics.sh --describe --bootstrap-server b-2.non-prod-***:9092 --topic. The config file should the increment though. Any idea on what am missing?

Hi again, based on question I'm assuming the config change that was made is related to number of partitions. Correct me if I'm wrong. If that is indeed the change you made, it applies only to the newly 'auto created' topics after the change has been made. This config doesn't change partition count of the existing topics. If you would like to change the partition count of existing topic, you can do so by running below command. Hope that answers!

./kafka-topics.sh --bootstrap-server <brokers> --alter --topic <topic> --partitions <new count>

follow up to build highly available clusters, won't happen data lost during patching upgrade

Use the following recommendations so that your MSK cluster can be highly available during an update (such as when you're updating the broker type or Apache Kafka version, for example) or when Amazon MSK is replacing a broker.

Set up a three-AZ cluster.

Ensure that the replication factor (RF) is at least 3. Note that a RF of 1 can lead to offline partitions during a rolling update; and a RF of 2 may lead to data loss.

Set minimum in-sync replicas (minISR) to at most RF - 1. A minISR that is equal to the RF can prevent producing to the cluster during a rolling update. A minISR of 2 allows three-way replicated topics to be available when one replica is offline.

Ensure client connection strings include at least one broker from each availability zone. Having multiple brokers in a client's connection string allows for failover when a specific broker is offline for an update. For information about how to get a connection string with multiple brokers, see Getting the bootstrap brokers for an Amazon MSK cluster.