[SERVER-30500] don't assign UUIDs to system.indexes on collMod/upgrade Created: 03/Aug/17  Updated: 30/Oct/23  Resolved: 09/Aug/17

Status: Closed
Project: Core Server
Component/s: MMAPv1, Storage
Affects Version/s: None
Fix Version/s: 3.5.12

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-08-21
Participants:
Linked BF Score: 0

 Description   

Assigning UUIDs to system.indexes on collMod causes inconsistencies between primaries and secondaries. Until SERVER-29926 is resolved, make sure to not upgrade them either.



 Comments   
Comment by Githook User [ 09/Aug/17 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria@mongodb.com'}

Message: SERVER-30500 do not assign UUIDs to system.indexes on collMod/upgrade
Branch: master
https://github.com/mongodb/mongo/commit/2de7b036fd98ba618d4a9cf4cbe1cf8e81132d48

Comment by Githook User [ 08/Aug/17 ]

Author:

{'name': 'Mathias Stearn', 'username': 'RedBeard0531', 'email': 'mathias@10gen.com'}

Message: Revert "SERVER-30500 do not assign UUIDs to system.indexes on collMod/upgrade"

This reverts commit 2d4c9492b8d2f0190fef1b7b758e49d63ef4659e.
Branch: master
https://github.com/mongodb/mongo/commit/f9e04ed194f8e995ab9f040798e5ffd6b14dad8d

Comment by Githook User [ 08/Aug/17 ]

Author:

{'username': 'mvankeulen94', 'email': 'maria@mongodb.com', 'name': 'Maria van Keulen'}

Message: SERVER-30500 do not assign UUIDs to system.indexes on collMod/upgrade
Branch: master
https://github.com/mongodb/mongo/commit/2d4c9492b8d2f0190fef1b7b758e49d63ef4659e

Comment by Ian Whalen (Inactive) [ 08/Aug/17 ]

milkie this is causing a pretty large number of build failures. I suspect we should pull this into the sprint and assign to someone other than Geert.

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