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 3 Next »


Changes

type key summary components parent status
Loading...
Refresh

Additionally, in dcb-service

v4.5.1

  • Search:

    • CRITICIAL reusing builder in Open Search causes immediate error

  • Cluster management: NA

  • FOLIO: NA

  • Polaris: NA

  • Logging and error checking: NA

  • Request and Circulation workflow: NA

  • GraphQL: NA

  • Sierra: NA

  • Miscellaneous: NA

Additionally, in dcb-devops

  • NA

Additionally, in dcb-admin-ui

  • NA

Additionally, in dcb-locate

  • NA

Deployment

Summary

Environments to deploy to:

  • Integration (tick)

  • Beta (tick)

Change Category

Required

Recommended

Not Required

Complete reset

(tick)

Environment configuration

(tick)

Host LMS configuration or setup

(tick)

Service configuration

(tick)

Ingest

(tick)

Index

(tick)

Library configuration

(tick)_

Deploy new Executables

(tick)

Instructions

It is important that this release is accompanied by a complete reset of the elastic search index. The ideal procedure is:

  1. Build the new DCB service

  2. Shut down DCB-Service

  3. curl -u "$ES_CREDS" -X DELETE "$ES_HOME/mobius-si"
  4. Because this will be a full reindex to introduce a new structure to the ES/OS mappings it will be more efficient to clean up two work tables in DCB. (warning) this step is a specific optimization in the dev/testing phase and should NOT be a normal op for DCB systems without specific instructions from the dev team.

    1. delete from cluster_record cr where cr.is_deleted = true and not exists ( select id from bib_record where contributes_to = cr.id )
    2. delete from shared_index_queue_entry; 

  5. Deploy the new service

  6. Startup

If this procedure is followed, dcb-service will recreate the missing mobius-si index at startup with the new definitions that include newer stopword and parsing definitions.

After resetting ops will need to post to the re-index endpoint to force a re-population of the new index structures:

curl -X POST $TARGET/admin/reindex -H "Accept-Language: en" -H "Content-Type: application/json"  -H "Authorization: Bearer $TOKEN" -d '{}'

Verification

After clear down

  • Check ES / OS to ensure there is no mobius-si index


After deployment

  • Check ES / OS to ensure the index is populating with records

  • No labels