Why is there a strict rule of number of brokers as multiple of AZ?
AWS MSK allows the number of brokers only as multiple of the number of availability zones selected.
It is recommended for a well-balanced infra, but why is has this been enforced?
I can't have 4/5 brokers in my 3 AZs & will therefore have to bear x2 cost instead.
We keep a consistent number of brokers across AZs and recommend that replication factors are set to at least 3 and replicas placed to ensure placement across all 3 AZs. This is intended to preserve the durability and availability of your cluster in case of a failure in an AZ. The availability aspect is the most significant factor in balancing brokers across AZs, since the loss of a single AZ in an unbalanced cluster would have a disproportional impact on the other two AZ's brokers, and lead to unpredictable availability. This explains why this is a best practice. The service design enforces this best practice, while simplifying operations, by keeping the broker numbers synchronized across AZs.
What is causing the excessive number of requests to s3?Accepted Answerasked 6 days ago
Number of Assets per Sitewise projectasked a year ago
Is there a limit on the number of QuickSight dashboards?Accepted Answerasked 3 years ago
Is there a limitation on the number of topics in IoT Core?Accepted Answerasked 2 years ago
Questions about networks of brokersasked 3 years ago
Max number of SQS as triggers for a single lambda?Accepted Answerasked 3 years ago
Get total number of array workers inside of array jobasked 6 months ago
Is there any limit to the number or age of events logged in CloudFormation event history?Accepted Answerasked 8 months ago
Why is there a strict rule of number of brokers as multiple of AZ?asked 9 months ago
How to estimate size and number of DMS instances for a given number of ongoing replicationsAccepted Answerasked 2 years ago