You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently AWS has make contributions to CC and create this BrokerSetAwareGoal in: #1809. This goal will ensure each topic (all its partitions and replicas) only lives within a single broker set.
Today we have a need to do partition level coloring, meaning a partition and all its replicas live within a broker set. Different partitions of a topic doesn't need to be in the same color. With the current BrokerSetAwareGoal, it is not allowed. I'm thinking about to add partition coloring by either update the BrokerSetAwareGoal, or make BrokerSetAwareGoal easily extendable to achieve it.
Basically there are 2 things we need to change:
For "ensureBrokerSetAware" method, we need to make it accept partition level coloring.
We need to remove the _mustHaveTopicLeadersPerBroker affect. In topic coloring, the rebalance should ignore those topics; while in partition coloring, the rebalance should not ignore those topics.
The text was updated successfully, but these errors were encountered:
Recently AWS has make contributions to CC and create this BrokerSetAwareGoal in: #1809. This goal will ensure each topic (all its partitions and replicas) only lives within a single broker set.
Today we have a need to do partition level coloring, meaning a partition and all its replicas live within a broker set. Different partitions of a topic doesn't need to be in the same color. With the current BrokerSetAwareGoal, it is not allowed. I'm thinking about to add partition coloring by either update the BrokerSetAwareGoal, or make BrokerSetAwareGoal easily extendable to achieve it.
Basically there are 2 things we need to change:
The text was updated successfully, but these errors were encountered: