[SERVER-27721] Implement rate limiter check for advancing logical clocks Created: 17/Jan/17  Updated: 05/Apr/17  Resolved: 17/Mar/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.1
Fix Version/s: 3.5.5

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Jack Mulrow
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-03-27
Participants:

 Description   

Also include maxAcceptableLogicalClockDrift parameter

// In secs for hybrid LogicalClock.
MONGO_EXPORT_STARTUP_SERVER_PARAMETER(maxAcceptableLogicalClockDrift, uint64_t,  365 * 24 * 60 * 60);
 
class LogicalClock {
public:
    ...
    // Assuming _myTime is mutex protected (as opposed to atomics)
    // Needs to be called in all cases where clock is being set, except for signAndAdvanceClusterTime
    Status passesRateLimiter_inlock(LogicalTime newTime) {
        auto now = secsNow();
        if (diff(newTime.getSecs() - now) > maxAcceptableLogicalClockDrift) {
            return ErrorCodes::ClusterTimeFailsRateLimiter;
        }
 
        return Status::OK()
    }
    ...
};



 Comments   
Comment by Githook User [ 17/Mar/17 ]

Author:

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

Message: SERVER-27721 Implement rate limiter check for advancing logical clocks
Branch: master
https://github.com/mongodb/mongo/commit/9c47a56c17f9c155f7794c09020893bfa80cb05d

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