A user had some issues after an upgrade put them on the unstable Juju path.
We've been working to get them back on stable and finally have them
upgraded to 1.20.1.

The issue we've run in to is that we have manually run an rs.initiate() to
get the replica set setup. When they jumped versions it was across the
non-HA / HA feature implementation. We have the proper IP and port in the
replica set.

The peergrouper is not aware of that replicaset and continues to report
this error. http://pastebin.ubuntu.com/7963471/

What collection do we need to update to so that the peergrouper is in sync
with the replicaset config?


-- 
Wayne Witzel III
[email protected]
-- 
Juju-dev mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Reply via email to