Details
-
Improvement
-
Resolution: Fixed
-
Major
-
7.1.4, 7.0.5, 7.2.0
-
Security Level: Public
-
0
-
Analytics Sprint 21, Analytics Sprint 22
Description
Currently we fail any rebalance once we encounter a dataset whose partitions do not have identical state. This should not be necessary:
- On a rebalance-in, we could simply skip any dataset(s) that we encounter this state. Once the states are in sync, the subsequent rebalance will rebalance the problematic dataset(s). This can be accomplished very quickly (unfortunately a bit late for 7.2.0).
I think we could allow the mismatched datasets to be rebalanced, reverting all DCP state to the earliest copy. We can then catch up any out-of-sync dataset(s) post-rebalance.
EDIT: will open another issue to consider #2 and other improvements- tracking #1 with this issue.
Attachments
Issue Links
- relates to
-
MB-56436 [System Test] Analytics rebalance operation failed with Analytics collections in different partitions have different DCP states error
- Closed
For Gerrit Dashboard: MB-56474 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
192897,10 | MB-56474: avoid CBAS0001 when not losing partitions in rebalance | neo | cbas-core | Status: MERGED | +2 | +1 |
192898,3 | MB-56474: avoid CBAS0001 when ds not losing partitions in rebalance | neo | cbas | Status: MERGED | +2 | +1 |