overleaf/services/history-v1
Eric Mc Sween 6077e73dd6 Merge pull request #13253 from overleaf/em-revert-leaked-socket-detection
Revert leaked socket detection

GitOrigin-RevId: 0f17864122a17fc69d0dac1ad5e2775805639871
2023-05-30 08:04:09 +00:00
..
api
benchmarks
config
migrations
storage Merge pull request #12904 from overleaf/bg-history-v1-streams-for-node-18 2023-05-10 08:04:51 +00:00
test
.gitignore
.mocharc.json
.nvmrc Merge pull request #12706 from overleaf/bg-rollback-broken-node-18-services 2023-04-20 08:03:54 +00:00
app.js Merge pull request #13253 from overleaf/em-revert-leaked-socket-detection 2023-05-30 08:04:09 +00:00
buildscript.txt Merge pull request #12706 from overleaf/bg-rollback-broken-node-18-services 2023-04-20 08:03:54 +00:00
docker-compose.ci.yml
docker-compose.yml Merge pull request #12706 from overleaf/bg-rollback-broken-node-18-services 2023-04-20 08:03:54 +00:00
Dockerfile Merge pull request #12935 from overleaf/jpa-include-patches 2023-05-05 08:04:13 +00:00
knexfile.js
Makefile
nodemon.json
package.json
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.