[SERVER-20265] Config servers need to always include $gleStats in their command responses if they are primary Created: 02/Sep/15 Updated: 25/Jan/17 Resolved: 21/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 9 (09/18/15), Sharding A (10/09/15) |
| Participants: |
| Description |
|
mongos uses $gleStats to work around commands that do not take write concern. For instance to create an index it runs createIndex, gets the optime after the insert from $gleStats, then uses that optime on a subsequent call to getLastError. SCCC config servers include $gleStats because they are always talked to over sharding-aware connections. We need to include $gleStats in command responses from CSRS config servers as well |
| Comments |
| Comment by Githook User [ 21/Sep/15 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Andy Schwerin [ 03/Sep/15 ] |
|
Should we do this by adding a metadata argument on commands sent to config servers, or just always include glestats in responses from csrs replica sets? |