![]() You can confirm from the logs about the final version: That way, just like Rocket.Chat, your MongoDB Docker instance is also ready for future updates. You can then go back to step 7a one more time and repeat the same process until 7c for MongoDB 5.0. Rocketchat_2 | | Commit Hash: 2ffdd13795 |Īt this stage, it is recommended to resume the database version upgrade, because the new Rocket.Chat is now compatible with MongoDB 5.0. Rocketchat_2 | | ReplicaSet OpLog: Enabled | Rocketchat_2 | | MongoDB Engine: wiredTiger | Rocketchat_2 | | MongoDB Version: 4.2.17 | Rocketchat_2 | | Rocket.Chat Version: 4.0.0 | You can also confirm from the logs about the new change: Sleep 20 & docker rm -f rocketchat_rocketchat_1ĭocker-compose up -d -scale rocketchat=1 -no-recreate Check the image version to 4.0.0 in the Docker Compose file and you're all set:ĭocker-compose up -d -scale rocketchat=2 -no-recreate Step 7d – Upgrade to Rocket.Chat 4.0.0Ĭongratulations, you are now completely ready to upgrade to the new version 4.0.0 because you are now on MongoDB 4.2! You can use scaling to activate a new instance of Rocket.Chat and minimize downtime. Now go back to step 7a and repeat the process until you have upgraded to version 4.2 and enabled feature support. "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), Waiting 30 secs." ĭocker-entrypoint.sh mongod -oplogSize 128 -replSet rs0 -storageEngine=wiredTiger " MONGO_OPLOG_URL=mongodb://mongo:27017/localĮcho "wiredTiger migration hasn't started yet. ![]() ![]() MONGO_URL=mongodb://mongo:27017/rocketchat ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |