Upgrade rocket chat to v. 7 #121
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just for the records
The main issue while upgrading was the upgrade of MongoDB.
The secondary replica was always failing at the initial sync. The diagnostic was: the data is already too big and syncing times out.
The solution was
sleep infinity./bitnami/mongodb/data/dbof the primary to the local machine and then to the same directory at the secondary.Until I got to the solution, had to face the problem that the logs were too big, eating all the storage of the secondary. I had to manually give more storage to the replica
rocket-chat-mongodb-0(it will remain so, namely 16G), but it wasn't enough. So that's the reason why we have now a limit for the logs (see e1cc85b).