RocketChat / RocketChat/Rocket.Chat

Clean install version 4.0.0 make huge disk usage.

Open
#23,434 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

Hello,

I did a clean install of rocketchat 4.0.0 5 days ago. in a docker container.

Before, I was on the 3.x branch.

I have found that between 3.x and 4 the disc constantly writes even though no one is using chat.

As soon as I cut the rocketchat container, the disk writes return to their normal level.

Steps to reproduce:

Nothing.

Expected behavior:

Normal hard drive usage

Actual behavior:

Heavy use of hard drive

Server Setup Information:
  • Version of Rocket.Chat Server: 4.0.0
  • Operating System: Synology
  • Deployment Method: docker (docker-compopse)
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 12.22.1
  • MongoDB Version: 4.4.9
Client Setup Information
  • Desktop App or Browser Version: 3.5.7
  • Operating System: Windows and Linux
Additional context

The server tells me that there are new messages but as the capture shows, there is nothing.
image

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 by reproducing the reported behavior with Rocket.Chat 4.0.0 in the stated Docker setup, comparing disk writes while the container is running and stopped. Inspect the server and MongoDB activity, since no source files or tests are identified. Done means identifying the source of the writes and confirming normal disk usage when the server is idle.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, mongodb, node.js
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.