Details
-
Bug
-
Resolution: Fixed
-
Critical
-
5.0.0
-
Untriaged
-
Yes
Description
Steps:
1. Setup a bixdr replication
2. Start loading data with bandwidth_limit set to 0
3. Pause replication, set bandwidth_limit to 1 and resume replication
4. Continue loading data
5. Wait for replication to catch up
6. Check to see if usage was less than limit after resuming replication
bandwidth_limit gets reset to 0 by StatsMgr as it detects a topology change while replication is going on (after setting limit to 1 and resuming):
2017-05-29T00:07:50.052-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_BandwidthThrottlerSvc bandwidth_limit=1048576, bandwidth_usage=953691
|
2017-05-29T00:07:50.081-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_ThroughSeqnoTracker time_spent=28.647478ms num_vb=1024 max_sent=4 avg_sent=0 max_filtered=0 avg_filtered=0 max_failed_cr=7 avg_failed_cr=2 max_gap=0 avg_gap=0
|
|
|
2017-05-29T00:07:50.116-07:00 INFO GOXDCR.ThrSeqTrackSvc: 4a55a033950afb73e5e7bb9082750955/default/default_ThroughSeqnoTracker GetThroughSeqnos completed after 2.527µs
|
2017-05-29T00:07:50.291-07:00 INFO GOXDCR.TopoChangeDet: ToplogyChangeDetectorSvc for pipeline 4a55a033950afb73e5e7bb9082750955/default/default validateSourceTopology completed
|
|
|
.....
|
|
|
2017-05-29T00:07:55.434-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_DataProcessedEventListener_1 chan size =0
|
2017-05-29T00:07:55.436-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_BandwidthThrottlerSvc bandwidth_limit=0, bandwidth_usage=0
|
2017-05-29T00:07:55.454-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_ThroughSeqnoTracker time_spent=18.353015ms num_vb=1024 max_sent=5 avg_sent=2 max_filtered=0 avg_filtered=0 max_failed_cr=5 avg_failed_cr=0 max_gap=0 avg_gap=0
|
|
|
2017-05-29T00:07:55.493-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default-355367636 counter docs_failed_cr_source goes backward, maybe due to the pipeline is restarted
|
2017-05-29T00:07:55.511-07:00 INFO GOXDCR.StatsMgr:
|
|
|
...
|
|
|
2017-05-29T00:07:59.978-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_DataSentEventListener_0 chan size =0
|
2017-05-29T00:07:59.978-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_DataReceivedEventListener_1 chan size =0
|
2017-05-29T00:07:59.978-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_DataThrottledEventListener_1 chan size =0
|
2017-05-29T00:07:59.978-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_BandwidthThrottlerSvc bandwidth_limit=1048576, bandwidth_usage=137269
|
2017-05-29T00:07:59.983-07:00 INFO GOXDCR.StatsMgr: 4a55a033950afb73e5e7bb9082750955/default/default_ThroughSeqnoTracker time_spent=4.319226ms num_vb=1024 max_sent=0 avg_sent=0 max_filtered=0 avg_filtered=0 max_failed_cr=1 avg_failed_cr=0 max_gap=0 avg_gap=0
|
Expectation is that limit does not get reset back to 0 automatically once set to a particular value