[SERVER-24465] Remove recoverShardingState parameter Created: 08/Jun/16 Updated: 25/Jan/17 Resolved: 26/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.8 |
| Fix Version/s: | 3.3.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | 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: | Minor Change | ||||||||||||||||||||
| Sprint: | Sharding 18 (08/05/16) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
And make sure that there will be no shard recovery if mongod started without --shardsvr |
| Comments |
| Comment by Spencer Brody (Inactive) [ 26/Jul/16 ] |
|
https://github.com/mongodb/mongo/commit/7daf57f28f564329e92b8779cf12845776b958b3 |
| Comment by Spencer Brody (Inactive) [ 21/Jul/16 ] |
|
As part of this we should also stop writing the shard name and config server connection string to the minOpTimeRecovery document, since it's redundant of the shardIdentity document. |