[DOCS-10763] Document that upgrading to 3.2.12 and 3.4.0 may cause initial sync to fail if collection renames are happening Created: 06/Sep/17  Updated: 13/Nov/23  Resolved: 09/Sep/17

Status: Closed
Project: Documentation
Component/s: manual, Rel Notes, Server
Affects Version/s: None
Fix Version/s: 3.2.12, 3.3.15, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Blocker - P1
Reporter: Spencer Brody (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-26117 renameCollection 'c' op should restar... Closed
Participants:
Days since reply: 6 years, 22 weeks, 4 days ago

 Description   

SERVER-26117 made it so that if initial sync encounters a renameCollection it will fail and restart, rather than proceeding and potentially corrupting data as it did in previous versions. Taht change is present starting in 3.2.12 and 3.4.0. We should make clear in the release notes for both that upgrading from 3.2.11- may cause initial syncs to start failing, especially if you are regularly using renameCollection or aggregation or mapReduce with $out (which performs a renameCollection internally)



 Comments   
Comment by Kay Kim (Inactive) [ 09/Sep/17 ]

[master] https://github.com/mongodb/docs/commit/49d8b0d78f09f9b96ee882086c6895f0f50fb1bf
[3.4] https://github.com/mongodb/docs/commit/309fcb42dda7894aae784a931d6e9a23663ed3db

[3.2] https://github.com/mongodb/docs/commit/279e271600001904d19970a8118e8a174b0772ce
https://github.com/mongodb/docs/commit/e8cf457d4229bbc7ab712652c3907cd0e8f4c074

Generated at Thu Feb 08 08:01:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.