[SERVER-37913] coll_epoch_test1.js does not wait for the config server to replicate after dropping collections. Created: 02/Nov/18  Updated: 29/Oct/23  Resolved: 05/Nov/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.1.4
Fix Version/s: 3.4.19, 3.6.10, 4.0.5, 4.1.5

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6, v3.4
Sprint: Sharding 2018-11-19
Participants:
Linked BF Score: 0

 Description   

When using a mongos that can have a stale afterOpTime (not using it to communicate with other nodes), it is crucial that we guarantee that the config server is always fully replicated. The afterOpTime is usually gossiped between the mongos and other nodes, so that any majority read request will have a certain minimum time to read at.

Failing to replicate in lieu of having an updated mongos afterOpTime can allow the mongos to read from a minority config server node that has an out-of-date majority commit point.



 Comments   
Comment by Githook User [ 16/Nov/18 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-37913 coll_epoch_test1.js does not wait for the config server to replicate after dropping collections

(cherry picked from commit 53cfb9e570e831e1388d0b9e24129d6f618ceded)
Branch: v3.4
https://github.com/mongodb/mongo/commit/c59376d6ced1b1d90f057238158b9503e3a836be

Comment by Githook User [ 16/Nov/18 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-37913 coll_epoch_test1.js does not wait for the config server to replicate after dropping collections

(cherry picked from commit 53cfb9e570e831e1388d0b9e24129d6f618ceded)
Branch: v3.6
https://github.com/mongodb/mongo/commit/c97d67c4ecfcea843f902f1c016ed21fb0ac589e

Comment by Githook User [ 16/Nov/18 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-37913 coll_epoch_test1.js does not wait for the config server to replicate after dropping collections

(cherry picked from commit 53cfb9e570e831e1388d0b9e24129d6f618ceded)
Branch: v4.0
https://github.com/mongodb/mongo/commit/31eb3db55b233fac8817de0d87cefd315944c63d

Comment by Githook User [ 05/Nov/18 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-37913 coll_epoch_test1.js does not wait for the config server to replicate after dropping collections
Branch: master
https://github.com/mongodb/mongo/commit/53cfb9e570e831e1388d0b9e24129d6f618ceded

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