[SERVER-20434] Allow mongos to store full OpTimes for GLE support Created: 16/Sep/15  Updated: 25/Jan/17  Resolved: 23/Sep/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: RPL A (10/09/15)
Participants:

 Description   

mongos needs to store OpTimes instead of Timestamps, in order to include the correct term when running GLE commands on shards.
In pv1, mongos will receive a valid term in the optime it gets as part of $gleStats. This term can be used in the wOpTime field of a subsequent GLE command, and everything should work as long as the shard remains in pv1.
In pv0, or from a 3.0 shard, mongos will receive no term in $gleStats. It will store a sentinel invalid term for such timestamps, and use just a timestamp for wOpTime in a subsequent GLE command.



 Comments   
Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-20434 Re-apply reverted 479900720 changes to replsets/ test
Branch: master
https://github.com/mongodb/mongo/commit/baa1d58dfeb0399c39d48de3aca3e2f1d29e102c

Comment by Githook User [ 23/Sep/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-20434 Allow mongos to store full OpTimes for GLE support
Branch: master
https://github.com/mongodb/mongo/commit/479900720b6da57c20a2956c3629375c361ffc59

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