Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.6.0
-
Untriaged
-
0
-
Unknown
Description
This was found during code inspection :
https://github.com/couchbase/plasma/blob/master/recovery.go#L1746
Justification :
During rebalance recovery at destination node, we can update the memory quota based on checkpoint data of a shard on source node. As the source and destination node can have different set of instances, the memory quota adjusted by memtuner may not be applicable to current node. Although mem-tuner can re-adjust quota based on RSS and free system memory, this can cause some jittery in performance during rebalance or slowness in overall rebalance duration if the updated memQuota is too low.
The fix should be simple and do not expect to cause regression.