Details
-
Improvement
-
Status: Closed
-
Trivial
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
When running RegionSplitter, our app devs noticed that they were getting a lot of NSREs. This is caused by 2 factors:
1. the split itself will cause an NSRE
2. any load balancing will cause one.
The former cannot be helped. We can more tightly control load balancing though. Instead of doing a name-sorted round-robin split across RS in the tier, we could sort the RS's by region count. That way, we only split an RS with 10 regions after there are no more RS with 9 regions. This will prevent the load balancing slop from kicking in and will fix the problem where restarting RegionSplitter always starts splitting at RS #1.