[SERVER-15399] Make the remote command execution in ReplicationExecutor::NetworkInterface asynchronous Created: 25/Sep/14 Updated: 25/Oct/14 Resolved: 06/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
This facilitates testing, and nearly obviates the need for a thread pool in the ReplicationExecutor itself. The implementation in mongod of the NetworkInterface will continue to use a thread pool for now, but it's no longer required, and the one in the unit tests will be thread-pool free. This makes it easier to write deterministic unit tests of network activity. |
| Comments |
| Comment by Githook User [ 06/Oct/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: Behavior is believed to match that of ScopedConn. |
| Comment by Githook User [ 06/Oct/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: Fully virtualizes time and network scheduling in NetworkInterfaceMock implementation, |