overleaf/services/history-v1
Jakob Ackermann 1dc2bd3a24 Merge pull request #15445 from overleaf/jpa-history-v1-gzip-in-place
[history-v1] gzip chunk string in-place before passing to object layer

GitOrigin-RevId: db5ded0b0db32757ed35c31c77d190bc121711a7
2023-10-26 08:03:41 +00:00
..
api Merge pull request #15410 from overleaf/jpa-history-v1-verbose-logging 2023-10-25 08:04:54 +00:00
benchmarks
config Merge pull request #15409 from overleaf/jpa-history-v1-http-timeout 2023-10-25 08:04:50 +00:00
migrations
storage Merge pull request #15445 from overleaf/jpa-history-v1-gzip-in-place 2023-10-26 08:03:41 +00:00
test Merge pull request #15382 from overleaf/csh-issue-11625-mongo-ug-5-history-v1 2023-10-26 08:03:38 +00:00
.gitignore
.mocharc.json
.nvmrc Merge pull request #14902 from overleaf/jpa-node-18-18-0 2023-09-25 08:04:25 +00:00
app.js Merge pull request #15409 from overleaf/jpa-history-v1-http-timeout 2023-10-25 08:04:50 +00:00
buildscript.txt Merge pull request #14698 from overleaf/bg-sg-use-node-watch 2023-10-03 08:04:36 +00:00
docker-compose.ci.yml
docker-compose.yml Merge pull request #14902 from overleaf/jpa-node-18-18-0 2023-09-25 08:04:25 +00:00
Dockerfile Merge pull request #14902 from overleaf/jpa-node-18-18-0 2023-09-25 08:04:25 +00:00
knexfile.js
Makefile Merge pull request #14902 from overleaf/jpa-node-18-18-0 2023-09-25 08:04:25 +00:00
package.json Merge pull request #15382 from overleaf/csh-issue-11625-mongo-ug-5-history-v1 2023-10-26 08:03:38 +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.