overleaf/services/history-v1
Christopher Hoskin cbaf1c3556 Merge pull request #13256 from overleaf/csh-issue-13004-max-retries
Increase the maximum retries for the delete-old-history-chunks cron job

GitOrigin-RevId: 8054ac76bbae24d0a3ba032c50c9647c044aef27
2023-06-02 08:07:17 +00:00
..
api
benchmarks
config Merge pull request #13256 from overleaf/csh-issue-13004-max-retries 2023-06-02 08:07:17 +00:00
migrations
storage Merge pull request #13256 from overleaf/csh-issue-13004-max-retries 2023-06-02 08:07:17 +00:00
test
.gitignore
.mocharc.json
.nvmrc
app.js Merge pull request #13255 from overleaf/em-socket-leak-detection 2023-05-31 08:05:24 +00:00
buildscript.txt Merge pull request #13251 from overleaf/msm-update-mongo-5 2023-06-01 08:05:18 +00:00
docker-compose.ci.yml Merge pull request #13274 from overleaf/csh-issue-13004-cleanup-custom-code 2023-06-02 08:05:10 +00:00
docker-compose.yml Merge pull request #13274 from overleaf/csh-issue-13004-cleanup-custom-code 2023-06-02 08:05:10 +00:00
Dockerfile
knexfile.js
Makefile
nodemon.json
package.json Merge pull request #12916 from overleaf/bg-move-stream-buffer-code-to-library 2023-06-02 08:05:57 +00:00
README.md

Database migrations

The history service uses knex to manage PostgreSQL migrations.

To create a new migrations, run:

npx knex migrate:make migration_name

To apply migrations, run:

npx knex migrate:latest

For more information, consult the knex migrations guide.

Global blobs

Global blobs are blobs that are shared between projects. The list of global blobs is stored in the projectHistoryGlobalBlobs Mongo collection and is read when the service starts. Changing the list of global blobs needs to be done carefully.

Adding a blob to the global blobs list

If we identify a blob that appears in many projects, we might want to move that blob to the global blobs list.

  1. Add a record for the blob to the projectHistoryGlobalBlobs collection.
  2. Restart the history service.
  3. Delete any corresponding project blobs.

Removing a blob from the global blobs list

Removing a blob from the global blobs list is trickier. As soon as the global blob is made unavailable, every project that needs the blob will have to get its own copy. To avoid disruptions, follow these steps:

  1. In the projectHistoryGlobalBlobs collection, set the demoted property to false on the global blob to remove. This will make the history system write new instances of this blob to project blobs, but still read from the global blob.

  2. Restart the history service.

  3. Copy the blob to all projects that need it.

  4. Remove the blob from the projectHistoryGlobalBlobs collection.

  5. Restart the history service.