[Sunflower] [ECS] Reindex for mod-search (Call Number Browse Refactor)

Description

App name/area of issue:

The implementation of the feature (UXPROD-4538: Call number browse refactorIn Review ) requires an assessment of the performance impact on

  • the reindex procedure.

  • data-import/bulk edit operations.

Brief statement of the issue:

The procedure for reindexing Call Numbers was refactored to improve maintainability and minimize complexity. The call numbers now have a separate search index. This may impact the performance of the reindex operation as well as ongoing indexing during data-import or bulk-edit.

  1. Measure reindex time and size of index for ECS mode and compare the results with PERF-984: [Ramsons] [ECS] Reindex for mod-search (reindex improvements)Closed

  2. Measure impact compared to previous release on data-import and bulk-edit

Steps to recreate the issue:

To start reindex - POST /search/index/instance-records/reindex/full
To check reindex status - GET /search/index/instance-records/reindex/status
For ECS start only on central tenant. Member tenants will start automatically

How many users at any given time:

ECS tenant environment

Volume of data:

Inventory:

  • Instances - 8M (Same Inventory ref data for central and members except 1) HRID settings and 2) locations)

Expected response time:

  • The whole reindexing procedure should take under 4 hours

  • The data-import and bulk-edit performance should not be affected more than 5%

Main modules that are involved in the process (if obvious or if known):

  • mod-inventory-storage

  • mod-search

Testing Approach:

  • Use Consorita cluster

  • Configure the environment to the one that FSE commonly uses.

  • Pause between sequential reindex processings is acceptable

  • Increase mod-search tasks count to 8

  • Upgrade OpenSearch instance type to at least 2x

  • The AWS RDS instance was configured to db.r6g.8xlarge, specifically optimized for reindexing and data loading. Downsize it once the process is complete.

  • The OpenSearch instance was also increased for the reindex to r6g.4xlarge.search

Acceptance Criteria:

  • Create a Confluence document based on the PTF report template, compare the results, highlight interesting observations and any necessary follow-up work.

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Natalia Zaitseva March 10, 2025 at 8:17 AM

Hello it will be included into Ramsons CSP

Martin Tran March 7, 2025 at 1:30 PM

What is the desired due date for this ticket? Will it be released in a Ramsons CSP or Sunflower GA?

Natalia Zaitseva March 6, 2025 at 12:24 PM

preliminary, the work related to Call-Number Browse Refactoring feature (Spitfire team) will be
deployed and ready for PTF testing on Monday MAR 10

cc:

Details

Assignee

Reporter

Priority

Development Team

PTF

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 6, 2025 at 6:21 AM
Updated March 10, 2025 at 8:17 AM
TestRail: Cases
TestRail: Runs

Flag notifications