[SERVER-22666] upgrade procedure testing for mongod instances aware that they are part of a sharded cluster Created: 16/Feb/16 Updated: 25/Jan/17 Resolved: 06/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Crystal Horn | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19 |
| Participants: |
| Comments |
| Comment by Githook User [ 06/Sep/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 06/Sep/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Esha Maharishi (Inactive) [ 30/Aug/16 ] |
|
Good idea; we have some pretty thorough unit tests of the retry logic, but no jstests: I'd recommend extending shard_aware_on_config_election.js to add cases where we need to retry, and maybe try to determine what additional coverage jstests could give: |
| Comment by Spencer Brody (Inactive) [ 30/Aug/16 ] |
|
As part of this, let's make sure to include that when the configsvr tries to insert the shardIdentity document on one of the shards it fails the first time, to test the retry logic. |