Skip to end of banner
Go to start of banner

2022-07-25 - Data Migration Subgroup Agenda and Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Date

Attendees

Carol Sterenberg, Jeffrey Fleming, Ian Wells, Lloyd Chittenden, Travis Brooks, Jeremy Nelson


Meeting Link

Link to Recordings

Discussion items

Time

Item

Who

Notes


Optimistic locking workarounds


Could disable all through testing phase, and always set _version = 1.  Or at least could test this.  Did anyone (especially Stanford) try this?


Stanford created an Airflow DAG for dropping the OL triggers for inventory tables, monitors running migration jobs, and restores the OL triggers after 5 minutes have elapsed since the last active migration job. Will be testing starting today.


Migration status/checkin
  • ByWater bringing up/migration small library to FOLIO this weekend

  • Stanford University Libraries were experiencing very poor performance with our on-prem Postgres database. Spending weeks trying different options/asking for help from the FOLIO community, here is summary of the different things we tried:

    • Move Postgres out of Kubernetes onto it's own VM
    • Drop inventory indices for Instances, Holdings, and Items
    • Drop SRS indexes
    • Drop SRS triggers
    • Upgrade an AWS FOLIO instance, Lotus and the SRS ingestion magnitudes better than our local Postgres

    After comparing the AWS RDS settings with our Postgres settings, we noticed that RDS had Just-in-Time turned off while our on-prem instances had JIT enabled. Turning off JIT locally fixed our issues!


Loading loans

For renewals, Have you tried migrating the loans as though they were were new and then changing both the loanDate and the dueDate via PUT, along with renewals count? That should avoid the immediate age-to-lost issue, and you don't have to create historical calendars to cover all of you possible loanDates. Your loan action history will indicate the change, but you should also be able to add an action comment when you make the update indicating that it was a migrated loan. This is roughly the technique used in folio_migration_tools .









Action items

  •  
  • No labels