[SERVER-4085] rs.initiate() command shouldn't return until replica set is ready for use Created: 17/Oct/11 Updated: 20/Feb/15 Resolved: 20/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently returns immediately with this message: "Config now saved locally. Should come online in about a minute." Then you must wait a while before using. This makes it harder to script tasks than if it would just not return until ready. |
| Comments |
| Comment by Eric Milkie [ 20/Feb/15 ] |
|
It's tough to define what "ready" is, because you can initiate() with a config that may never elect a primary (or it might eventually elect a primary hours later, once connections are established to other nodes). |