[SERVER-28293] Add LogicalTimeMetadata handling outside of metadata section in mongod Created: 13/Mar/17  Updated: 06/Dec/17  Resolved: 02/Jun/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.4
Fix Version/s: 3.5.9

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, Sharding 2017-04-17, Sharding 2017-05-08, Sharding 2017-05-29, Sharding 2017-06-19
Participants:

 Description   

Verify that mongod process $logicalTime object similarly to mongos. This change should include a test case to run the logical_time_api.js mongod in a shareded cluster.



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

Author:

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

Message: SERVER-28293 Verify mongod processes $logicalTime like mongos
Branch: master
https://github.com/mongodb/mongo/commit/8162f04849106dc40adccfc479dd6aa6b6bfde2a

Comment by Misha Tyulenev [ 01/Jun/17 ]

Updated the description.

Comment by Jack Mulrow [ 30/May/17 ]

misha.tyulenev, it looks like Mathias's work has already made mongod both send and handle logical time metadata in the command body. I verified this by updating logical_time_api.js to expect $logicalTime in the response's command body instead of metadata and by having it pass higher clusterTimes through $logicalTime in requests and expect the server's clusterTime to increase (with auth off).

Should we update this ticket to only update the logical_time_api.js test? Or something else?

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