Juju Charms Collection
mongodb package

Race condition when deploying a simple replica set

Bug #1267222 reported by Jorge Castro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mongodb (Juju Charms Collection)
Fix Released
Undecided
Juan L. Negron

Bug Description

Doing a

juju deploy mongodb
juju add-unit mongodb -n4

results in some nodes not coming up, you can resolve it with `juju resolve mongodb/# --retry` to fix the unit.

I noticed this error before I tried the retry:

           19:22:40.165 [initandlisten] ERROR: can't use --slave or --master replication options with --replSet

Tags: audit

Related branches

lp:charms/mongodb
Juan L. Negron (negronjl)
Changed in mongodb (Juju Charms Collection):
assignee: nobody → Juan L. Negron (negronjl)
Jorge Castro (jorge)
tags: added: audit
Revision history for this message
Juan L. Negron (negronjl) wrote :

I'm working on this now.

-Juan

Changed in mongodb (Juju Charms Collection):
status: New → In Progress
Revision history for this message
Juan L. Negron (negronjl) wrote :

There is logic in hooks.py that sets the deployment as master or slave. This logic doesn't take into account replica sets and it should.

If we can determine wether a mongodb instance is part of a replica set then we can eliminate the --master or --slave <master> from the start line.

-Juan

I'll try to work something out for this.

Revision history for this message
Juan L. Negron (negronjl) wrote :

Fixed in revision 44.

-Juan

Changed in mongodb (Juju Charms Collection):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.