[SERVER-38524] Rename collection in initial sync Created: 11/Dec/18  Updated: 14/Dec/18  Resolved: 11/Dec/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.6.9
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Ankur Goyal Assignee: Danny Hatcher (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-4941 collection rename may not replicate /... Closed
Participants:

 Description   

rename collection does not support in initial sync after 3.2.11.

Currently i am using 3.4.2 3, i upgraded slave (which i want to initial sync) to 3.6.9, but issue persisted same. Please help in which version this bug is fixed or any alternate for the same.



 Comments   
Comment by Ankur Goyal [ 14/Dec/18 ]

Thanks Danial for last explanation.

Comment by Danny Hatcher (Inactive) [ 12/Dec/18 ]

To clarify a little more, this operation should work in 3.6 but only if both the source and destination nodes are on 3.6. It is failing in this case because the source is on 3.4.

Comment by Danny Hatcher (Inactive) [ 11/Dec/18 ]

Hello Ankur,

This was a known issue tracked in SERVER-4941. Please look to that ticket for an explanation of the issue, known workarounds for your version, and to identify the fix version as 3.6.0.

Thank you,

Danny

Generated at Thu Feb 08 04:49:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.