Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
7.0.2
-
None
-
Untriaged
-
1
-
Unknown
Description
This was seen in 7.0.2.
I was mainly trying to see the UI XDCR --> Scopes & Collections to Replicate behavior when the scope box was checked, and I saw this replication behavior which I wasn't sure was the expected/intended behavior. (Neil asked me to open an MB.)
The below UI selection ends up creating these mapping rules (source: travel-sample, target: test-bucket2):
% couchbase-cli xdcr-replicate --cluster localhost --username Administrator --password mypassword --get --xdcr-replicator 596673660096c4a4e414cc99418e3561/travel-sample/test-bucket2
|
|
{
|
"checkpointInterval": 600,
|
"colMappingRules": {
|
"inventory": "inventory",
|
"inventory.airport": "inventory.airport1",
|
"inventory.landmark": "inventory.landmark1"
|
},
|
"collectionsExplicitMapping": true,
|
"collectionsMigrationMode": false,
|
"collectionsMirroringMode": false,
|
"collectionsOSOMode": true,
|
"compressionType": "Auto",
|
"desiredLatency": 50,
|
"docBatchSizeKb": 2048,
|
"failureRestartInterval": 10,
|
"filterBypassExpiry": false,
|
"filterDeletion": false,
|
"filterExpiration": false,
|
"filterExpression": "",
|
"hlvPruningWindowSec": 259200,
|
"jsFunctionTimeoutMs": 20000,
|
"logLevel": "Info",
|
"mergeFunctionMapping": {},
|
"networkUsageLimit": 0,
|
"optimisticReplicationThreshold": 256,
|
"pauseRequested": false,
|
"priority": "High",
|
"retryOnRemoteAuthErr": true,
|
"retryOnRemoteAuthErrMaxWaitSec": 3600,
|
"sourceNozzlePerNode": 2,
|
"statsInterval": 1000,
|
"targetNozzlePerNode": 2,
|
"type": "xmem",
|
"workerBatchSize": 500
|
}
|
|
The target bucket test-bucket2 has scope inventory and inside scope inventory, seven collections – airline, airport, landmark, route, hotel, landmark1, airport1 – before the XDCR replication starts, all of the collections are empty.
After the XDCR replication starts, all of the target bucket's 7 collections are correctly populated. Just want to be sure that this is the expected/intended behavior.
Attachments
Issue Links
- is caused by
-
MB-49192 XDCR - collections data ignored path could leads to panic
- Closed