Details
-
Bug
-
Resolution: Fixed
-
Minor
-
6.6.3, 7.0.3, 7.1.0
-
Untriaged
-
1
-
Unknown
Description
Resource manager will:
- Check replication status
- Check replication priorities
- Compute the necessary actions based on priority
When all replications have the same priority, there will be no throttling action and step 1 above may be unnecessary especially when it adds to contention with ns_server's goxdcr_stats_collector and causes dropped ticks when there is a large number of replications.
Issue | Resolution |
There was an issue in the ns_server stats collector when the Resource Manager checked the pipeline status to obtain the replication priority to provide more resources for higher priority pipelines. | Resource Manager does not now check replication pipeline statuses when all replication pipelines have either the exact same high or low priority. |
Attachments
Issue Links
- is a backport of
-
MB-52002 Resource manager should not check replication status if all replication has the same priority
- Closed
For Gerrit Dashboard: MB-56847 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
190892,1 | MB-56847: Don't perform resource management if all replications have the same priority, either high or low. | 7.1.4 | goxdcr | Status: ABANDONED | 0 | 0 |
191073,3 | MB-56847: Don't perform resource management if all replications have the same priority, either high or low. | 7.1.x | goxdcr | Status: MERGED | +2 | +1 |