[SERVER-29941] mongos_does_not_gossip_logical_time_without_keys.js should only expect one generation of keys Created: 30/Jun/17  Updated: 30/Oct/23  Resolved: 05/Jul/17

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

When two keys have to be inserted by the config server primary, it does so serially, so there can be a delay between creating the first and second keys. mongos_does_not_gossip_logical_time_without_keys.js asserts there are at least two keys after it has received a signed logical time in the response from mongos, but it's possible mongos has only read the first key from the config servers, and this assertion could fail even though the second key is about to finish being inserted.



 Comments   
Comment by Githook User [ 05/Jul/17 ]

Author:

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

Message: SERVER-29941 mongos_does_not_gossip_logical_time_without_keys.js should expect one key
Branch: master
https://github.com/mongodb/mongo/commit/1323edbe69bc44d6911169486de33fb59233ff8f

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