RocketChat / RocketChat/Rocket.Chat
Change Database Schema Migration Schedule
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
NODE CPU automatically goes high and lead to Rocketchat down. It needs to do docker-compose restart to bring RC UP.
We found that there is RC's database schema migration process happening everyday at confirmed time which is a creating a problem for us and affecting during business hours.
Expected behavior:
We should be able to change RC's database schema migration schedule and able to set it during night time to not impact RC resources usage during business hours.
Actual behavior:
RC database schema migration process is running everyday at confirmed time but we are not able to change this schedule.
Server Setup Information:
Server Setup Information:
Version of Rocket.Chat Server: 6.2.2
Operating System: Ubuntu 20.04.6 LTS
Deployment Method: Docker
Number of Running Instances: 1
DB Replicaset Oplog: Yes
NodeJS Version: 14.21.2 - x64
MongoDB Version: 5.0.15
MongoDB Engine: wiredTiger
USE_NATIVE_OPLOG=true
Client Setup Information
Client Setup Information
Desktop App: App 3.8.13
Operating System: Ubuntu 22.04.2 LTS
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
The issue reports a daily database schema migration in a Docker deployment and requests a configurable schedule. No source file, test, or entry point is named; first identify the migration scheduler and its configuration path, then define how a changed schedule should be configured and verified without affecting business hours.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mongodb, node.js, typescript, ubuntu
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100