[SERVER-23814] Add sharding state initialization to secondaries Created: 19/Apr/16 Updated: 25/Jan/17 Resolved: 26/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.4 |
| Fix Version/s: | 3.3.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | 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 |
| Sprint: | Sharding 14 (05/13/16) |
| Participants: |
| Comments |
| Comment by Githook User [ 26/Apr/16 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Outside of the OpObserver, there are currently 2 places where shard initialization occurs: during startup and during transition to primary. This patch takes out the if !replSet condition in startup so secondaries will now also perform shard initialization. This also means that if the node will eventually become a primary, it will perform the initialization twice. However, since it is already initialized, most of it will be no-op the second time around. In summary:
|