[BOOKKEEPER-1105] RackAwarePolicy: Failure to map node into rack may result in failure to add other nodes.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.5.0
• Fix Version/s: 4.6.0, 4.5.1
• Component/s: bookkeeper-client, bookkeeper-server
• Assignee: Andrey Yegorov
• Reporter: Andrey Yegorov
• Created: 09/Aug/17 18:25
• Updated: 16/Aug/17 13:31
• Resolved: 16/Aug/17 01:42

Description

Ran into this issue:
due to some misconfiguration of new node and rack assignments we've ended up with nodes being assigned to default rack. We are not using region-aware, only rack-aware policy.
This generates the following sequence of events:

• default rack is /default-region/default-rack even though region-aware is not used.
• other nodes mapped to racks like /rack1, /rack2 etc.
• mixing /region/rack and /rack styles is not allowed, but exception on addition of such nodes is swallowed. All following nodes to add (if there were any) just skipped as result.