Cannot deploy a replica set with desired number of units
Bug #1470124 reported by
Casey Marshall
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MongoDB Charm |
Fix Released
|
High
|
Mario Splivalo | ||
Bug Description
From the mongodb charm README:
> Replica Sets
> Deploying
>
> Deploy the first two MongoDB instances that will form replicaset:
>
> juju deployu mongodb -n 2
>
> Deploying three or more units at start can sometimes lead to unexpected race-conditions so it's best to start with two nodes.
This complicates automated deployment of mongodb from an ops perspective. This charm should fix the race-condition and allow deployment of a replica set of the desired size.
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in mongodb (Juju Charms Collection): | |
| assignee: | nobody → Mario Splivalo (mariosplivalo) |
| status: | New → Confirmed |
| affects: | mongodb (Juju Charms Collection) → mongodb-charm |
| Changed in mongodb-charm: | |
| status: | Confirmed → In Progress |
| importance: | Undecided → High |
Revision history for this message
| Mario Splivalo (mariosplivalo) wrote | #2 |
| Changed in mongodb-charm: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fixing this requires leadership, and thus Juju 1.23 or later.