How do you do your Mongo upgrades? Do you use ansible playbooks in the configuration repo? There are some playbooks in particular that seem to me like they might be unmaintained cruft that I’d like to get rid of, but I’m curious is anyone’s using them. In particular mongo_rolling_upgrade.yml and mongo_upgrade_hidden_secondaries.yml. As they reference the Mongo 3.0 playbook, I suspect they haven’t been useful for a long time without local modification.
We’re currently halfway through upgrading edx.org from Mongo 3.2 to 3.6. Right now we’re on 3.4 on the way to 3.6, as Mongo requires upgrading one major release at a time. This means that Juniper will likely involve upgrading Mongo from 3.2 to 3.6 in two steps. I don’t know if there’s any precedence for upgrading Mongo by more than one release at a time, per named release. Is there any automated process from openedx that upgrades mongo for openedx operators or do you usually upgrade Mongo manually or using your own custom process? Our process is to spin up new nodes on the new version using the playbooks, joining them to the cluster, migrating to the new nodes and then shutting down the old nodes.