search

toconnell / kdm-manager

An interactive campaign manager for the game "Monster", by Kingdom Death. Development blog and release notes at https://blog.kdm-manager.com This project has no affiliation with Kingdom Death and is a totally independent, fan-maintained project.
http://kdm-manager.com
Other
26 stars 11 forks source link

MDB data stuck in 2.6 db; main host cannot do-release-upgrade #511

Closed toconnell closed 5 years ago

toconnell commented 6 years ago

Current DB is 2.6 and the next Ubuntu wants to jump straight from 2.6 to 3.6.

Doing so will cause the server to not start because the data is incompatible. From mona, where I hit the issue this morning:

2018-08-21T08:11:10.378-0500 F CONTROL  [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details.

The docs (referenced in the error above) want you to do this:

db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )

...but the production DB is so old that it doesn't support setting that param:

toconnell@ubuntu-trusty-1:~$ mongo
MongoDB shell version: 2.6.10
connecting to: test
> db.version()
2.6.10
> db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
{ "ok" : 0, "errmsg" : "no option found to get" }
>
toconnell commented 6 years ago

This is really bad.

toconnell commented 6 years ago

Just recording my thoughts for posterity here, but this seems like a vote in favor of starting the move to Firebase.

Maybe we move the DB off of the local provision and into Firebase and then start slowly moving the rest of the app...

toconnell commented 5 years ago

The July migration makes this issue moot.

The new host has:

db version v3.6.3
git version: 9586e557d54ef70f9ca4b43c26892cd55257e1a5
OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
allocator: tcmalloc
modules: none
build environment:
    distarch: x86_64
    target_arch: x86_64