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
Consume from the topic using a consumer group (prompts creation of consumer offsets topic)
Decommission broker 2 via "rpk brokers decommission"
Observe /v1/brokers -- broker 2 remains in state 'draining' indefinitely.
This scenario does work if you have never done anything that prompted an internal topic creation, e.g. if you never did that consumer group operation.
Suggested fix:
At the admin API level: if node count is 3, and any partitions exist with replicas=3 (other than controller topic), and internal_topic_replication_factor >= 3, then refuse any decom request.
If internal_topic_replication_factor == 1 and any internal topics are at replicas=3, then when we receive such a decom request, decrease the replication factor of those topics before trying to do the decom. This provides a path for users who really genuinely want to shrink their cluster to a point where they put data at risk. The default for internal_topic_replciation_factor is 3, so only users who manually adjust it will be able to do this -- default to data safety.
@jcsp was broker 2 ever put into maintenance mode? also, maybe we are talking about 'draining' in a different context like draining the partitions as part of the decommission process?
@dotnwat this is the membership_state::draining, rather than the maintenance mode draining. In retrospect we probably should have picked a different noun for one of these
When we address this + test shrinks from >=3 to <3 nodes, should also check for maintenance mode and refuse to shrink to <3 nodes if any of the nodes are currently in maintenance mode (see #4921)
@dotnwat this is the membership_state::draining, rather than the maintenance mode draining. In retrospect we probably should have picked a different noun for one of these
i'll see what i can do to rename the maintenance mode draining state.
This scenario does work if you have never done anything that prompted an internal topic creation, e.g. if you never did that consumer group operation.
Suggested fix:
JIRA Link: CORE-896
The text was updated successfully, but these errors were encountered: