Details
-
Bug
-
Resolution: Duplicate
-
Major
-
7.1.0
-
7.1.0-1312
-
Untriaged
-
Centos 64-bit
-
1
-
Unknown
Description
I setup replication from magma bucket "GleamBookUsers0" on src cluster: 172.23.110.64 to couchstore bucket "destBkt" on target cluster: 172.23.110.70. This led to the issue described in: MB-48559.
After this, I paused the replication, deleted the couchstore bucket on target and added a magma bucket with the same name. The paused replication was gone in the UI, so I created it again. The replication does not get created, xdcr seems to be stuck in a loop:
2021-09-22T15:04:02.448-07:00 ERRO GOXDCR.RemClusterSvc: Original REST request (http://172.23.110.70:8091/pools/default/buckets/destbkt) received Requested resource not found.^M
|
response. The URL may be incorrect or requested resource no longer exists
|
2021-09-22T15:04:02.448-07:00 ERRO GOXDCR.BucketTopologySvc: BucketTopologySvcWatcher for local? false bucket destbkt updating resulted in err Bucket doesn't exist - bypassing notification
|
2021-09-22T15:04:03.293-07:00 INFO GOXDCR.GenericSupervisor: Send heartbeat failed for AdminportSupervisor, err=Last heart beat msg has not been processed
|
2021-09-22T15:04:05.628-07:00 INFO GOXDCR.HttpServer: Executing Action timed out
|
2021-09-22T15:04:05.629-07:00 INFO GOXDCR.HttpServer: ****************************
|
2021-09-22T15:04:05.629-07:00 ERRO GOXDCR.HttpServer: Execution timed out
|
2021-09-22T15:04:05.629-07:00 ERRO GOXDCR.HttpServer: Execution timed out
|
2021-09-22T15:04:06.293-07:00 INFO GOXDCR.GenericSupervisor: Send heartbeat failed for AdminportSupervisor, err=Last heart beat msg has not been processed
|
Attachments
Issue Links
- duplicates
-
MB-48559 [30TB test]: XDCR replications are stuck at 11.116G mutations remaining since hours. Total Data at source is 28TB(10B items).
- Closed