[SERVER-23800] Remove ShardConnection::sync Created: 19/Apr/16 Updated: 26/Apr/16 Resolved: 20/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 13 (04/22/16) | ||||||||
| Participants: | |||||||||
| Description |
|
The ShardConnection::sync call goes through all sharded connections in use and calls getLastError in order to synchronize with all outstanding fire-and-forget operations. Since all write operations are running as commands and as of 3.2 all configuration calls are using w:majority with journaling, this is no longer necessary. |
| Comments |
| Comment by Githook User [ 20/Apr/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |