[SERVER-46371] Error messages and logging should not assume collection was dropped and recreated on epoch change Created: 24/Feb/20  Updated: 29/Oct/23  Resolved: 11/Mar/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-03-09, Sharding 2020-03-23
Participants:

 Description   

There are a few places where we log or return an error message when a sharded collection's epoch changes that assume the collection was dropped and recreated (e.g. here). Previously this was correct, but as of 4.4 refining a collection's shard key can also change the epoch, so such messages/logs are misleading and should be updated.



 Comments   
Comment by Githook User [ 30/Mar/20 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-46371 Don't assume epoch change implies drop/create in logging, error messages, and comments

(cherry picked from commit fd2016f77b3ef55d6bb63e83110bde456d693883)
Branch: v4.4
https://github.com/mongodb/mongo/commit/84d954a70c1c948787061f74df0b71e3efe52511

Comment by Githook User [ 11/Mar/20 ]

Author:

{'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-46371 Don't assume epoch change implies drop/create in logging, error messages, and comments
Branch: master
https://github.com/mongodb/mongo/commit/fd2016f77b3ef55d6bb63e83110bde456d693883

Generated at Thu Feb 08 05:11:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.