[SERVER-21187] Make getNextGlobalTimestamp lock-free Created: 28/Oct/15  Updated: 17/Nov/15  Resolved: 06/Nov/15

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: 3.2.0-rc1
Fix Version/s: 3.2.0-rc3

Type: Improvement Priority: Minor - P4
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QuInt C (11/23/15)
Participants:

 Description   

This is currently a critical section using a mutex, which may become a bottleneck after we remove other mutexes.



 Comments   
Comment by Eric Milkie [ 09/Nov/15 ]

Was there a code review for this?

Comment by Githook User [ 06/Nov/15 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-21187: Don't use mutexes for updating globalTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/b1c0d15ff77effd81201096cb52a9959711b7000

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