[SERVER-35105] Applying renameCollection not supported in initial sync Created: 20/May/18 Updated: 28/Jun/18 Resolved: 21/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.6.3, 3.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cezary Bartosiak | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | initialSync, renameCollection | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We have 5 instances in our replica set: 1. ARBITER, 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):
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... |
| Comments |
| Comment by Ramon Fernandez Marina [ 22/May/18 ] |
|
cbartosiak, we've filed Regards, |
| Comment by Cezary Bartosiak [ 21/May/18 ] |
|
Thank you for confirming my assumption. The current attempt is at 50 % now and I can see messages like: createCollection: [...] with provided UUID [...], so it looks like it should work now. Maybe it is a good idea to add a warning at startup (like for XFS), isn't it? It is an important setting and it's so easy to forget about it. |
| Comment by Ramon Fernandez Marina [ 21/May/18 ] |
|
cbartosiak, you're indeed hitting As you've found out, if your other nodes had featureCompatibilityVersion set to 3.4 the upgrade to 3.6 is not complete yet. Fully upgrading to 3.6 should take care of this issue, so I'm going to close this ticket as a duplicate of Thanks, |
| Comment by Cezary Bartosiak [ 20/May/18 ] |
|
My coloring has gone, but it's clear what's going on. I also pasted a link to another, closed issue (gone as well): https://jira.mongodb.org/browse/SERVER-4941 EDIT: I checked featureCompatibilityVersion setting and... it shows 3.4! It looks like a mistake done during an upgrade of the old instance. I will update this comment after another attempt is finished to let you know if changing it to 3.6 helps. |