[SERVER-1973] A server started with --slave can only be changed by re-starting process Created: 19/Oct/10 Updated: 10/Dec/14 Resolved: 02/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Shell |
| Affects Version/s: | 1.6.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Gaetan Voyer-Perrault | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Any |
||
| Participants: |
| Description |
|
In short if a server is started as --slave the slave status can only be changed by re-starting the process. Ideally, a shell command would be able to remove slaving status. In the same way a shell command should be able to promote a slave to master. This feature is particularly useful for switching between master & slaves (which is currently a little dicey). |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 19/Oct/10 ] |
|
This is probably not something we're going to do. For most cases - we think replica sets are the right thing to use which do this automatically. For manual cases, we want to keep things as simple as possible. |