[SERVER-10766] Always write lastmodEpoch field on config.collections Created: 13/Sep/13  Updated: 11/Jul/16  Resolved: 14/Sep/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.5.2
Fix Version/s: 2.5.3

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-10758 Strict Epoch comparison Closed
Operating System: ALL
Participants:

 Description   

If you shard a collection and drop it, the epoch field will not be present.



 Comments   
Comment by auto [ 14/Sep/13 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-10766 Always write lastmodEpoch field on config.collections
Branch: master
https://github.com/mongodb/mongo/commit/9c477e581a2be731e43dd1271b88e6e450c32acd

Comment by auto [ 14/Sep/13 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-10766 Always write lastmodEpoch field on config.collections

Introduce the dropped version constants for ChunkVersion.
Branch: master
https://github.com/mongodb/mongo/commit/e2e5928c784e37d6cd29270d7e891f02ebf28fbc

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