-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Attachments take ages to upload and view #24266
Comments
That is the reason. You could use migrator tool: GitHub - RocketChat/filestore-migrator |
Will the migration tool migrate all existing attachments ? |
I don't know actually, I saw that advice here We are using S3 from start without any performance issues. |
I have the same issue. #24225 |
OK. So it seems the mongorestore while upgrading failed to created the indexes on all of the rocketchat_uploads / rocketchat_uploads.files / rocketchat_uploads.chunks collections. This is also true for the rocketchat_avatar collections These collections are currently set as gridFS and the amount of time to upload a new file or view an existing file is just unbearable. Does anybody know where I can find a current list of the indexes that should exists on collections for RocketChat Version 4.3.2 Regards |
Hi, i have the same thing (runnig docker images) ... looooooading very slow. I used the migration tool also did a fresh import from the backup. always the same issue. I also went thrue the Versions 3.18.5 Mongo DB Upgrade ... then Mongo 4.2 (chat 4.4.2) same issues. Database is running local around 5 GB big. Any progress on this topic. |
I had the same issue Standalone setup
Docker setup
|
Thank you for your effort, i will try this ASAP and leave feedback here. |
I actually use MongoDB Compass and luckily had another install I could find the indexes for. Next... Change gridfs to use an S3 bucket |
For anybody running into this using snap: To get into mongo:
To find databases:
List will show up. Identify database that holds rocket tables. (parties in my case)
Verify table is there:
And then do the thing
Let it do it's thing.
|
Artem thanks it works! |
This is NOT True!
This is true and fixes the issue for me too in a RC 6.0 Setup. Thank you! |
Thanks. We had massive problems with high CPU and Block I/O after the upgrade. This fixed it for us. We were using the official RC manual. This step is missing.
Thank you |
In my case it doesn't work `MongoServerError: Executor error during find command :: caused by :: Sort exceeded memory limit of 104857600 bytes, but did not opt in to external sorting. UP: so that there are no errors when exporting user data
|
We have an issue after upgrading our Rocket.Chat install to the latests, server / client and MongoDB (see versions below)
After upgrading, first to wiredTiger, then to version 4.2 / 4.4 then 5.0 all attachments added to chats i.e. images / audio / video etc take an inordinate amount of time.
Also clicking on these attachments also take an inordinate amount of time to show or start playing.
By inordinate I mean 3 - 5 minutes to show images or upload new attachments as oppose to just a few seconds previously.
None of our attachments are particularly large and affect ALL existing attachments (viewing) and new attachments (upload and or view)
The stack trace
I get the following stack traces in the Rocket.Chat logs which seems to indicate a missing parameter OR missing indexes. Any ideas how to fix this will be appreciated..
ufs: cannot read file "mC3nrWQ3cY7ifoJwz" (Executor error during find command :: caused by :: Sort exceeded memory limit of 104857600 bytes, but did not opt in to external sorting.) MongoError: Executor error during find command :: caused by :: Sort exceeded memory limit of 104857600 bytes, but did not opt in to external sorting.
at MessageStream.messageHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connection.js:272:20)
at MessageStream.emit (events.js:314:20)
at MessageStream.EventEmitter.emit (domain.js:483:12)
at processIncomingData (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
at MessageStream._write (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
at doWrite (_stream_writable.js:403:12)
at writeOrBuffer (_stream_writable.js:387:5)
at MessageStream.Writable.write (_stream_writable.js:318:11)
at Socket.ondata (_stream_readable.js:718:22)
at Socket.emit (events.js:314:20)
at Socket.EventEmitter.emit (domain.js:483:12)
at addChunk (_stream_readable.js:297:12)
at readableAddChunk (stream_readable.js:272:9)
at Socket.Readable.push (stream_readable.js:213:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
at TCP.callbackTrampoline (internal/async_hooks.js:126:14) {
ok: 0,
code: 292,
codeName: 'QueryExceededMemoryLimitNoDiskUseAllowed',
'$clusterTime': {
clusterTime: Timestamp { bsontype: 'Timestamp', low: 2, high: 1642705737 },
signature: { hash: [Binary], keyId: 0 }
},
operationTime: Timestamp { bsontype: 'Timestamp', low: 2, high: 1642705737 }
Server Setup Information:
Client Setup Information
Steve
The text was updated successfully, but these errors were encountered: