RocketChat / RocketChat/Rocket.Chat

Exploding .wt collection file

Open
#32,307 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

I have a wired tiger file in /var/snap/rocketchat-server/common that increases 10-20GB per day, currently at 100GB. Our server is running out of disk space constantly.

Would like to trace what it happening here. Our group is not uploading large files and we do not have a large team.

Steps to reproduce:
  1. Navigate to /var/snap/rocketchat-server/common
  2. Check large files in directory
  3. See large .wt file -> -rw------- 1 root root 108925952000 Apr 24 00:27 collection-48--77318xxx37791.wt
Expected behavior:

Expect reasonable database and .wt file sizes considering the amount of data we put into rocketchat

Actual behavior:

Exploding .wt file size

Server Setup Information:
  • Version of Rocket.Chat Server: 6.7.0
  • Operating System: Ubuntu 18.04
  • Deployment Method: Snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Desktop App or Browser Version: Brave 1.64.122
  • Operating System: Debian 12
Additional context
Relevant logs:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported /var/snap/rocketchat-server/common path and collection-48--77318xxx37791.wt file, then gather the missing MongoDB version and relevant server logs. Done means identifying what is causing the file to grow and documenting or implementing a verified resolution that keeps database size reasonable.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.