[SERVER-27828] Pass ServiceContext to oplog and ReplicationCoordintor methods that will use LogicalClock Created: 26/Jan/17  Updated: 05/Apr/17  Resolved: 08/Feb/17

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-02-13
Participants:

 Description   

This is the prep work for allow LogicalClock that will be a decoration on the ServiceContext without calling getGlobalServiceContext().

That will include passing a ServiceContext pointer to
setNewTimestamp()
getNextOpTime() - already has OpeartionContext
ReplicationCoordinatorImpl::_performPostMemberStateUpdateAction
ReplicationCoordinatorImpl::_setCurrentRSConfig_inlock
fixDocumentForInsert
ModifierCurrentDate::apply
fixupTimestamps

will NOT change the OplogReplaySlaveReadTill::run()

There will be no new tests , as the only anticipated problems are possible compile and dependencies issues.



 Comments   
Comment by Githook User [ 08/Feb/17 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-27828: Pass ServiceContext to oplog and ReplicationCoordinator methods that will use LogicalClock
Branch: master
https://github.com/mongodb/mongo/commit/437352cd7dbc158343e2929888d265928b6ca8b7

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