Page MenuHomeSoftware Heritage

Separate indexer db to its own postgresql cluster
Closed, MigratedEdits Locked

Description

Move indexer db to its own cluster.

Unfortunately, when separated from the storage db, it has been moved to the replica cluster (T867).
As the replication tool backups the cluster fully, that would mean yet another replication of the replica db which is a nogo (due to disk space!).

That will ease its backup (T880).

Event Timeline

After discussion, the new cluster can stay on somerset.

ardumont changed the task status from Open to Work in Progress.Feb 7 2018, 12:17 PM
ardumont renamed this task from Separate indexer db to its own cluster to Separate indexer db to its own postgresql cluster.Feb 7 2018, 12:24 PM

Road so far:

  • somerset - Create cluster
  • somerset - Create needed roles (swhstorage, guest)
  • somerset - Create db
  • swh-workers - Stop indexers
  • Update swh-site/swh-private-data accordingly ( (local swh-site + swh-private-data commits done)
  • somerset - Migrate old db data to the new one
  • Check data consistency between dbs (content_mimetype, fossology_license, etc...)
  • Deploy changes to relevant machines: indexer storage server (uffizi)
  • swh-workers - Restart indexers
  • Ensure everything is fine regarding indexer restart (db)
  • somerset - Drop old softwareheritage-indexer db on cluster 5433 (reclaim space)