Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.3.6
Affects Version/s: None
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 13 (04/22/16), Sharding 14 (05/13/16)
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Now that config servers will start making connections back to shards, we should have the ShardRegistry available to facilitate that communication.

is related to

SERVER-22649 Expand TaskExecutor use. Ensure that a TaskExecutor always is available in mongod

Closed

SERVER-23139 ShardRegistry on config servers should read the registry information from local storage

Closed

SERVER-24072 config server should persistently store it's own name

Closed

Assignee:: Randolph Tan
Reporter:: Spencer Brody (Inactive)
Participants:: Githook User, Randolph Tan, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 14 2016 02:53:15 PM UTC
Updated:: Jan 25 2017 09:59:06 PM UTC
Resolved:: May 06 2016 09:09:34 PM UTC
Confidence Status Last Update:: 05/May/16 8:15 PM