Tier config with invalid tenant fails on rebalance with NPE
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 2d 55m
- Merged PRs (30d)
- 182
Description
If a tier config is added with an invalid tenant, the table config update is succeeds but a rebalance of the table returns with an NPE. Then to find the exact error the controller logs need to be searched.
Is that intended as a tenant may not always be present? Or should adding a tier config that contains a tag which does not point to any instance fail when updating the table config?
Contributor guide
Research direction
Start by reproducing the table config update with a tier config containing an invalid tenant, then trigger a table rebalance. Inspect the controller logs alongside the rebalance result to determine the expected handling; done means the behavior for a missing tenant is explicitly decided and the NPE is no longer the user-visible outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100