[SERVER-23427] Add test to ensure that read-only operations against the config db continue to work if the config server primary is unreachable from mongos Created: 30/Mar/16 Updated: 25/Jan/17 Resolved: 11/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | 3.3.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding 13 (04/22/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Original Title and description: Some read-only operations (eg count,aggregate) fail against the config database when the config server primary is unreachable |
| Comments |
| Comment by Githook User [ 11/Apr/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 11/Apr/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 08/Apr/16 ] |
|
The reason count doesn't work in 3.2 when the primary config is unreachable is due to I will leave this ticket open just for the addition of the new jstest I wrote to prevent regressions here. |
| Comment by Spencer Brody (Inactive) [ 30/Mar/16 ] |
|
Attaching jstest that reproduces this issue in 3.2 |