Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document what to do *after* migration #2

Open
mhow2 opened this issue Oct 28, 2021 · 3 comments
Open

document what to do *after* migration #2

mhow2 opened this issue Oct 28, 2021 · 3 comments

Comments

@mhow2
Copy link

mhow2 commented Oct 28, 2021

Hi,
I've successfully applied the migration to WiredTiger, however we are left with a transitional docker-compose.yml. Maybe a good thing would be to document what to do with this file after the migration. Things I'm thinking:

  • remove the dependency to the migrator service
  • cleanup the local folder (remove docker folder).
  • what do to with the while loop in mongo service waiting for WiredTiger migration ?
@mhow2
Copy link
Author

mhow2 commented Nov 16, 2021

@frdmn what do you think ?

@lwsystems
Copy link

After finnishing migration, I've changed the old compose file in the following way.
Set mongo version to 4.2 and start the mongo process with
command: mongod --oplogSize 128 --replSet rs0 --storageEngine=wiredTiger
After upgrade, images seemed to be loaded very slow. But I've no idea if this is an mongo issue.

@ChetanGoti
Copy link

@lwsystems I faced the same issue after I migrated to wiredTiger engine. (I'm using GridFS)

It seems the index is missing on the attachments. Creating an index as mentioned at RocketChat/Rocket.Chat#24266 (comment) fixed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants