[SERVER-29785] shards should not gossip $logicalTime and operationTime if FCV is set to 3.4 Created: 21/Jun/17  Updated: 30/Oct/23  Resolved: 23/Jun/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.10

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

Issue Links:
Depends
is depended on by SERVER-29754 Remove checks for featureCompatibilit... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-07-10
Participants:

 Description   

Similar to mongos in SERVER-29652, shards and configs should not gossip $logicalTime if FCV is set to 3.4.
While its unlikely that client will connect directly we should avoid the scenario when the afterCLusterTime clause is rejected but operationTime is still returned because its hard to address on the client side.

In mongod the FCV is available hence the implementation is the following
1. add a check that FCV == 36 in https://github.com/mongodb/mongo/blob/master/src/mongo/db/service_entry_point_mongod.cpp#L484
so the operationTime will be added only in 36 mongod for sharded and standalone RS

2. add a check that FCV == 36 in
https://github.com/mongodb/mongo/blob/master/src/mongo/db/service_entry_point_mongod.cpp#L257-L268
so the operationTime will be added only in 36 mongod for sharded and standalone RS



 Comments   
Comment by Githook User [ 23/Jun/17 ]

Author:

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

Message: SERVER-29785 shards and config should not gossip logicalTime and operationTime if FCV is 3.4
Branch: master
https://github.com/mongodb/mongo/commit/2800021bafc2c006f88d6d640a02a30f2c4231da

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