Skip to end of banner
Go to start of banner

<TBD>mod-search: Test Reindexing of Instances (Poppy) multi-tenant

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

Overview

  • The purpose of the document is to to identify how ECS-related changes are affecting reindexing on multi tenant environment. Calculate reindex time and size of index.

Recommendations & Jiras

Test Summary

Reindexing on 3 tenants in parallel takes the same time as reindexing on main tenant only. If to start in sequential order from secondary tenants it may take more time for main tenant afterwards (25 minutes more). The reason may be less resource utilization from CPU side (mod-search-44% against 38% and mod-inventory-storage - 20% against 19%).

Comparing interim results of indexing size it was found that the major time during reindexing was taken by contributor and instance_subject indexing.

Test Runs /Results

Test #

Instances number

Test Conditions

reindexing on Poppy release

Duration 

Notes


1. 2023_10_12 08:47 - 18:32 UTC


In parallel: 3 tenants

9 hours 45 min
  • mod-search task count =8
  • mod-inventory-storage task count = 2
  • mod-okapi task count = 3
  • open search instance scaled up to r6g.4xlarge.search
  • without configuration of number_of_replicas and refresh_interval values of ES/OpenSearch

2. 2023-10-13 09:04 - 09:07 UTC

100032

In sequential: fs09000002

3 min

3. 2023-10-13 09:15 - 09:18 UTC

100055

In sequential: fs09000003

3 min
4. 2023-10-13 09:29 - 19:37 UTC10,733,729In sequential: fs0900000010 hours 8 min

Indexing size

Test #1 Here I would like to share interim results during reindexing on 3 tenants. In 30 minutes after start we observe that all instances on secondary tenants have been already indexed except of ocp2_contributor_fs09000002 without 1 record. In 2 hours after the start we observe that docs.count column for instances on main tenant has all records but reindexing goes on with previously mentioned contributor_fs09000000 and instance_subject_fs09000000.

So we may conclude that major of time for reindexing goes to contributor indexing (at least 7 hours out of 9 hours 45 min).

ALL tenants

AFTER START: < date: Thu, 12 Oct 2023 09:18:08 GMT
< date: Thu, 12 Oct 2023 10:01:46 GMT
< date: Thu, 12 Oct 2023 10:53:10 GMT
AFTER FINISH: < date: Fri, 13 Oct 2023 08:07:06 GMT
healthstatusindexuuidprirepdocs.countdocs.deletedstore.sizepri.store.size
prirepdocs.countdocs.deletedstore.sizepri.store.size
prirepdocs.countdocs.deletedstore.sizepri.store.size
prirepdocs.countdocs.deletedstore.sizepri.store.size
greenopenocp2_instance_fs09000000NyClr4AYR9CUqEPeQOuzkg424215098060.8gb20.5gb
4281616940105.5gb35.1gb
42107337290140.1gb46.5gb
42107337290124.2gb41.3gb
greenopenocp2_instance_fs09000003QoBX9DqsR7S8XLJ-VpFPUA421000553554.8mb181.5mb
421000553554.8mb181.5mb
421000553554.8mb181.5mb
421000553554.8mb181.5mb
greenopenocp2_instance_fs0900000286NVpQwqSAWeUmmd1506Gg421000320550.3mb180mb
421000320550.3mb180mb
421000320550.3mb180mb
421000320550.3mb180mb
greenopen.kibana_19Q4bvyKCRpiiwcPNcLFs9g121015.5kb5.1kb
121015.5kb5.1kb
121015.5kb5.1kb
121015.5kb5.1kb
greenopenocp2_authority_fs09000003RGz9CTCoT7CoT3H3ge5gIA42002.4kb832b
42002.4kb832b
42002.4kb832b
42002.4kb832b
greenopen.opensearch-observabilitykPAJ8TqaR06AQZFYekHeyA1200624b208b
1200624b208b
1200624b208b
1200624b208b
greenopenocp2_authority_fs09000002vFMI3x8bTuqp5HkAL3jk8A42002.4kb832b
42002.4kb832b
42002.4kb832b
42002.4kb832b
greenopenocp2_authority_fs09000000YCS4y0GFTfy3EpbJm99X0g42002.4kb832b
42002.4kb832b
42002.4kb832b
42002.4kb832b
greenopenocp2_contributor_fs09000000rmhGKwfISJiayaxyO8C03w4219671401927878.1gb2.5gb
42305742164005711.8gb4.2gb
42324967971169436.1gb12.8gb
42407609833222618.8gb5.1gb
greenopenocp2_instance_subject_fs09000000N4X98pwsTRGs9ZiO8ia-0A42183717737500618.2gb6.1gb
42264391654157632.5gb11.2gb
42384868480002014gb4.4gb
42463398561434012.1gb4.1gb
greenopenocp2_contributor_fs09000003aBDxrr83SpaxBlqORzFdUQ42372811gb249.2mb
4237262517.4mb169.2mb
4237262391.8mb43.6mb
4237262391.8mb43.6mb
greenopenocp2_instance_subject_fs090000020CwHeq53T3yHkY62fDoNyw42900608.2kb58.2kb
42900608.2kb58.2kb
42900608.2kb58.2kb
42900608.2kb58.2kb
greenopenocp2_contributor_fs090000020XXn4kfrTAG5Wpdouwyaxg42368100600.2mb194.9mb
423693831.1gb338.9mb
42369161460.8mb90.5mb
42369161460.8mb90.5mb
greenopenocp2_instance_subject_fs09000003Dsibsz4NQ2WxvQQviAO4zA42950391.4kb59.5kb
42950391.4kb59.5kb
42950391.4kb59.5kb
42950391.4kb59.5kb

Test #2

fs09000002







healthstatusindexuuidprirepdocs.countdocs.deletedstore.sizepri.store.size
greenopenocp2_instance_fs09000002Pd2I7_Q8Rj2bNgSP4vSzIg421000320579mb190.3mb
greenopenocp2_authority_fs09000002vFMI3x8bTuqp5HkAL3jk8A42002.4kb832b
greenopenocp2_instance_subject_fs090000023vfuyqMBRlGtmblChed_LA42945413.9kb136.5kb
greenopenocp2_contributor_fs09000002xgXcKSDWR3W2IYC6JiFqSA423691238696.8mb165.4mb
Test #3







fs09000003







healthstatusindexuuidprirepdocs.countdocs.deletedstore.sizepri.store.size
greenopenocp2_instance_fs09000003YjbGBqXpRG6ap03WlRFokw421000550579.8mb190.8mb
greenopenocp2_authority_fs09000003RGz9CTCoT7CoT3H3ge5gIA42002.4kb832b
greenopenocp2_contributor_fs09000003O4SdQSXqT_y2UapCuer6GQ4237261853mb259.1mb
greenopenocp2_instance_subject_fs090000032P6hQELJTWKYqvJ5l-5jTw42986413.6kb136.3kb
Test #4







fs09000000







healthstatusindexuuidprirepdocs.countdocs.deletedstore.sizepri.store.size
greenopenocp2_instance_fs09000000VIviDunkSkinkiZJuMjKUQ42107337290119.6gb39.9gb
greenopenocp2_authority_fs09000000YCS4y0GFTfy3EpbJm99X0g42002.4kb832b
greenopenocp2_contributor_fs090000002kdpF4fZTaGtFmG_ypXq6A42466665961250312.2gb4.1gb
greenopenocp2_instance_subject_fs09000000q3wktVUgTsmElTq6Iv-p2A42409701165883917.8gb6.1gb

Memory Usage

Test #1

mod-search max. 70% during an hour, 60% - during second hour

mod-inventory-storage avr. 28%

Test #2, 3 secondary tenants

mod-search max. 50%

mod-inventory-storage avr. 26%

Test #4 main tenant

mod-search max. 70% during an hour, 60% - during second hour

mod-inventory-storage avr. 28%


Memory consumption

Test #Module

Initial spike

1

mod-search70%
mod-inventory-storage28%
2mod-search50%
mod-inventory-storage26%
3mod-search50%
mod-inventory-storage26%
4

mod-search70%
mod-inventory-storage28%

CPU Utilization 

Test #1

mod-search - 44%

mod-inventory-storage - 20%

Test #2, 3 secondary tenants

mod-search - 10%

mod-inventory-storage - 10%

Test #4 main tenant

mod-search - 38%

mod-inventory-storage - 19%

CPU utilization

Test #Module

Initial spike

1

mod-search44%
mod-inventory-storage20%
2mod-search10%
mod-inventory-storage10%
3mod-search10%
mod-inventory-storage10%
4

mod-search38%
mod-inventory-storage19%

RDS CPU Utilization 

Test #1

Utilization max. - 72%


Test #2, 3 secondary tenants

Utilization max. - 42%

Test #4 main tenant

Utilization max. - 65%

Open Search KPIs

CPU utilization

Test #1

Max. 89%

Test #2, 3 secondary tenants

Max. 32%

Test #4 main tenant

Max. 88%

Indexing rate

Test #1

Test #2, 3 secondary tenants

Test #4 main tenant


Indexing latency 

Test #1

Test #2, 3 secondary tenants

Test #4 main tenant

Appendix

Infrastructure

PTF -environment ocp2

  • 10 m6i.2xlarge EC2 instances located in US East (N. Virginia)us-east-1 
  • 2 instances of db.r6g.xlarge database instances, one reader, and one writer 
  • MSK ptf-kakfa-3
    • 4 m5.2xlarge brokers in 2 zones
    • Apache Kafka version 2.8.0

    • EBS storage volume per broker 300 GiB

    • auto.create.topics.enable=true
    • log.retention.minutes=480
    • default.replication.factor=3

Number of instances

ocp2 -10M 

Kafka partitioning


Poppy

inventory.item

50

inventory.instance

50

inventory.holdings-record

50

inventory.bound-with

50

inventory.authorit

50

search.instance-contributor

50



Modules memory and CPU parameters:

Modules

Version

Task Definition

Running Tasks 

CPU

Memory

MemoryReservation

MaxMetaspaceSize

Xmx

mod-search Poppy3.0.0-SNAPSHOT.156682048259224805121440
mod-inventory-storage Poppy26.1.0-SNAPSHOT.6851122048409636905123076
mod-search Orchid 
2.1.0-SNAPSHOT.108
384002592248010241440
mod-inventory-storage Orchid26.1.0-SNAPSHOT.644321024195222085121440


Methodology/Approach

  • Use Consorita cluster with Poppy release, which has 10M records, to test with (2 times)
  • Configure the environment in accordance with Infrastructure parameters  to the one that FSE commonly uses
  • Reindex on the new Poppy environment, get the results for indexing time, index size
  • Create a comparison of results between sequential order and parallel start.


  • No labels