replicaset configuration cannot be removed from existing units
Bug #1868265 reported by
Adam Dyess
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MongoDB Charm |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
I encountered a situation where the two mongo-dbs were in existence creating a replicaset between the two. More may have been added later, but at some point it was decided to reduce to just one unit.
The charm didn't recognize this and remove the replica-set configuration (maybe it shouldn't) but there were no juju actions or juju config to help mongo it wasn't running as a cluster anymore.
as a work around:
ssh into the unit
remove any mention of replSet from the config
# comments weren't good enough b/c the charm looks for presence of a string
add 'master = true'
service mongodb restart
| Changed in charm-mongodb: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Eric Chen (eric-chen) wrote | #1 |
| Changed in charm-mongodb: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
This charm is no longer being actively maintained. Please consider using the new mongodb-
https:/
I will close this feature request