[SERVER-20869] Add support for probabilistic loss of MongoDB messages in mongobridge Created: 11/Oct/15  Updated: 17/Nov/15  Resolved: 11/Nov/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.2.0-rc3

Type: New Feature Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-19301 Create new interface for network part... Closed
Backwards Compatibility: Fully Compatible
Sprint: QuInt B (11/02/15), TIG B (10/30/15), QuInt C (11/23/15)
Participants:

 Description   

Should work with both discarding the requests that mongobridge receives and discarding the responses that mongobridge receives. Note that 100% loss is sufficient for representing a network blackhole in our testing scenarios.



 Comments   
Comment by Githook User [ 11/Nov/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-20869 Include cstdint in mongobridge.h.
Branch: master
https://github.com/mongodb/mongo/commit/80dfa9ff4da8935ff294483e14ad5a6cdcd05985

Comment by Githook User [ 10/Nov/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-20869 Fix compile by doing .as<long> instead of .as<int64_t>.
Branch: master
https://github.com/mongodb/mongo/commit/37a6559c83f602f14f079771c911b19188f23654

Comment by Max Hirschhorn [ 10/Nov/15 ]

Reopening because doing .as<int64_t> broke compile on certain platforms.

Comment by Githook User [ 10/Nov/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-20869 Add support for probabilistically discarding messages.
Branch: master
https://github.com/mongodb/mongo/commit/e586fad588424e86631c6fb7f5d3eb3faa451c08

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