Recreate OpenSearch index for ezid-stg post graviton migration

[jsjiang]

Refreshed the ezid-stg RDS with prd database; recreate OpenSearch index post graviton migration.

Related tickets:

• Migrate EZID Stage RDS to graviton #971
• Reduce opensearch index update script log output #975

[jsjiang]

Reindex logs:

• Started on 12/18, 4pm
• checked on 12/19, 8am:
  • process stopped at mid-night
  • indexed 4.96m identifiers in 8 hours; average 620K/hour; may take 5 days to finish 37m identifiers
  • log file size: 3M
• restarted indexing process 12/19, 4pm
  • with log settings that only produces the request log at the ERROR level;
  • starting_id 12732415
  • process stopped after one hour at 5pm

TO-DO:

• Request large instances (EC2 & RDS) first thing in the new year for running the OpenSearch indexing & performing load tests

'loggers': {
            '': {
                #'handlers': ['request_log', 'trace_log', 'ecs_json'],
                'handlers': ['request_log'],
                'propagate': True,
                'level': 'ERROR',

python -u manage.py opensearch-update --starting_id 12732415 > ../logs/opensearch_update_1218.log.3 &

[1] 1690481

[jsjiang]

• Requested instance upgrade (EC2 and RDS) with IAS (Jan 5, 2026) https://github.com/cdlib/cdlsys/issues/974
• Rerun OpenSearch indexing after instance upgrade