RocketChat / RocketChat/Rocket.Chat
snap server stuck at elevated cpu usage after 12h
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
CPU-usage rises steeply after 12h uptime.
Steps to reproduce:
snap install rocketchat-server
Configure the Server.
Expected behavior:
It just seems like a very unnatural spike, which is why i think that it is probably a bug.
Actual behavior:
Spike after exactly 12h uptime.
Server Setup Information:
- Version of Rocket.Chat Server:
2.4.14 - Operating System:
Ubuntu 20.04 - Deployment Method:
snap - Number of Running Instances:
1 - DB Replicaset Oplog:
don't know what that is - NodeJS Version:
don't know how i can get this info out of a snap packet - MongoDB Version:
don't know how i can get this info out of a snap packet
Client Setup Information
no client used
Additional context
Surely i can just restart the server every 11 hours, but that shouldn't be the way to go.
Relevant logs:
unsure what would be helpful here
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the snap installation and monitoring CPU usage through 12 hours on Ubuntu 20.04 with Rocket.Chat 2.4.14. Gather the relevant server, Node.js, MongoDB, and snap logs and identify what causes the spike; done means the cause is isolated and CPU usage no longer rises unexpectedly after prolonged uptime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, node.js, ubuntu
- Domain
- backend, devops, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100