-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.6.3, 3.6.4
-
Component/s: Replication
-
ALL
We have 5 instances in our replica set:
1. ARBITER, Mongo 3.6.4, Ubuntu 16.04
2. PRIMARY, Mongo 3.6.4, Ubuntu 16.04
3. SECONDARY, Mongo 3.6.4, Ubuntu 16.04
4. SECONDARY, Mongo 3.6.3, Debian 8.1
5. NEW MEMBER, Mongo 3.6.4, Ubuntu 16.04
The 4th member was a primary in the past and its data were cloned using a snapshot (we are in a cloud) to create members 2 and 3. What's important it had Mongo 3.4, but we had upgraded it before proceeding with replication. Now we are trying to attach another member, but we want it to be synchronized via an initial sync because we want it to have a different data structure (separate folders for databases). Unfortunately the initial sync was running for more than 40 hours and restarted because of the following error (colored by me):
2018-05-20T18:11:27.888+0000 I STORAGE [repl writer worker 10] createCollection: <anonymized>.tmp.agg_out.253 with no UUID.
2018-05-20T18:11:27.903+0000 E REPL [repl writer worker 4] Error applying operation: OplogOperationUnsupported: Applying renameCollection not supported in initial sync: { ts: Timestamp(1526688414, 116), t: 10, h: 8574474825826084483, v: 2, op: "c", ns: "<anonymized>.$cmd", wall: new Date(1526688414589), o: { renameCollection: "<anonymized>.tmp.agg_out.253", to: "<anonymized>.mime_types", stayTemp: false, dropTarget: true } } ({ ts: Timestamp(1526688414, 116), t: 10, h: 8574474825826084483, v: 2, op: "c", ns: "<anonymized>.$cmd", wall: new Date(1526688414589), o: { renameCollection: "<anonymized>.tmp.agg_out.253", to: "<anonymized>.mime_types", stayTemp: false, dropTarget: true } })
2018-05-20T18:11:27.904+0000 E REPL [replication-515] Failed to apply batch due to 'OplogOperationUnsupported: error applying batch :: caused by :: Applying renameCollection not supported in initial sync: { ts: Timestamp(1526688414, 116), t: 10, h: 8574474825826084483, v: 2, op: "c", ns: "<anonymized>.$cmd", wall: new Date(1526688414589), o: { renameCollection: "<anonymized>.tmp.agg_out.253", to: "<anonymized>.mime_types", stayTemp: false, dropTarget: true } }'
As far as I understand this kind of error was a bug in earlier versions of Mongo and should not happen in our case. However I can see createCollection [...] with no UUID which looks strange according to what I've read so far about this issue.
Unfortunately we cannot stop aggregations, so we will surely have more these $out commands which makes me not very optimistic in terms of next attempts...
- duplicates
-
-
- Closed
-
- related to
-
SERVER-35140 Add a startupWarning if running in the previous FCV version relative to your binary version
-
- Closed
-