Environment taking too long to upgrade (Reindexing is extremely slow)

Riya Ray
Riya Ray
  • Updated

Author: Riya Ray

Date: October 16, 2023

Audience: Everyone

Environmental details: 

  • Recently upgraded to Jama Connect® 8.74.1 (Self-Hosted, Air-gapped: DEV) from Jama Connect® 8.62.2
  • Database: MySQL 8.0
  • Docker Version: 20.10.7
  • Replicated Version: 2.53.2
  • Application Server OS: CentOS

Problem/Summary:

When users upgrade to a new version, it is required for them to perform a full reindex on their instance. Sometimes, users need help with problems where the reindexing speed becomes extremely slow and takes an unusual amount of time to complete.

Solution:

To improve the Reindexing process, check the following points:

  1. Check CPU and RAM resources: Ensure that the instance is set up with sufficient resources for both CPU Cores and the RAM. Check the below articles for Jama's recommendations:
    1. Resource Sizing for Application Server (Traditional)
    2. Resource Sizing for Application Server (KOTS)
    3. Resource Sizing for Database Server (KOTS)
  2. Ensure mysql.conf file is correctly set up.
  3. Ensure Advanced Memory settings are enabled and correctly set up per this article
  4. Add the following parameters to the Replicated console to improve Reindexing. These values should be updated on Advanced Startup Settings under Add services configuration (key=value pairs on separate lines) text box. With these configurations, we are increasing the system capabilities and the load it can process per item.
    • reindexBrokenItemThreshold=1000000
    • jamasearch.multithreadindex.enabled=true
    • jamasearch.multithreadindex.chunksize=500
    • jamasearch.multithreadindex.poolsize=10
    • jamasearch.tenantReindexingMaxPayloadSizeInBytes=5242880
    • tenantReindexingMaxPayloadSizeInBytes=5242880
  5. For many users on their instances, the performance (especially relating to the reindexing) has improved after running the below SQL commands. Run the below queries on the database server, followed by a full reindex (traditional/ kots) from the root (traditional/ kots) menu. 
    • mysqldump db_name > dump.sql 
    • mysql db_name < dump.sql
  6. If the above also does not fix the issue, user may need to force the database to update the database index stats by running the below query:
    • mysqlcheck -u root -p --auto-repair --optimize contour

Additional Information/Metadata:

  • Performance
  • Slowness
  • Full Reindexing
  • Troubleshooting

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.