[allura:tickets] #8348 Support mongo 3.6+ DOCKER CHANGES

[Dave Brondsema <da...@brondsema.net>]

- **summary**: Support mongo 3.6+ --> Support mongo 3.6+  DOCKER CHANGES
- **Comment**:

## Upgrade notes if using Docker

`docker-compose.yml` and `docker-compose-prod.yml` updated Mongo from 3.4 to 4.2 but it is not possible to upgrade that far all at once.  Older installations may have mongo in a 3.2 compatibility mode as well.  To upgrade a docker instance:

* connect to the running mongo `docker-compose run --rm mongo mongo --host mongo project-data`
* check its compatibility version (may be lower than actual installed version) `db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )`
* if needed, update it to match installed 3.4 version `db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )`
* then upgrade one version at a time:
    *  update `docker-compose.yml` one version (e.g. `mongo:3.6`)
    *  stop mongo `docker-compose stop mongo`
    *  restart mongo with newer version `docker-compose up -d`
    *  connect to the running mongo `docker-compose run --rm mongo mongo --host mongo project-data`
    *  set the compatibility version to match `db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )`
    *  repeat for 4.0 and again for 4.2

Refer to the offical docs for more details:
https://docs.mongodb.com/manual/release-notes/3.4/#upgrade-procedures
https://docs.mongodb.com/manual/release-notes/3.6/#upgrade-procedures
https://docs.mongodb.com/manual/release-notes/4.0/#upgrade-procedures
https://docs.mongodb.com/manual/release-notes/4.2/#upgrade-procedures



---

** [tickets:#8348] Support mongo 3.6+  DOCKER CHANGES**

**Status:** invalid
**Milestone:** unreleased
**Created:** Wed Jan 22, 2020 07:13 PM UTC by Dave Brondsema
**Last Updated:** Fri Feb 21, 2020 05:18 PM UTC
**Owner:** Dave Brondsema


Reported initially at [#7935] this occurs during a project export, probably other places too:
```
OperationFailure: command SON([('aggregate', u'attachment.files'),
('pipeline', [{'$match': {'_id': {'$in': []}}}, {'$group': {'total_size':
{'$sum': '$length'}, '_id': 'total'}}, {'$project': {'total_size':
{'$divide': ['$total_size', 1000000]}, '_id': 0}}])]) on namespace
project-data.$cmd failed: The 'cursor' option is required, except for
aggregate with the explain argument
```


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.