[SERVER-23973] Ensure that config servers send the appropriate optime and config server connection string when making request to shards Created: 28/Apr/16 Updated: 25/Jan/17 Resolved: 23/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.8 |
| Type: | Task | 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 | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 15 (06/03/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
We currently rely on the ShardingEgressMetadataHook to send the config server optime whenever making a request to a shard. This loads the optime off the grid. For config servers making requests to shards we need to either fetch the optime from the replication coordinator directly or ensure that the optime in grid is maintained properly. |
| Comments |
| Comment by Githook User [ 24/May/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 23/May/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 19/May/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 28/Apr/16 ] |
|
As part of this, re-evaluate whether Shard.cpp should be passing in the Repl metadata to ShardLocal::_runCommand. It might be that for local operations run on the config server we want to fetch and maintain the optime in a different way. |