Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

ElasticSearch fails after upgrading to 7.1.9

SA-14222

Summary



After upgrading from 7.1.8 to 7.1.9 ElasticSearch is throwing WARN messages about unavailable shards.
 

Error Messages



2015-09-08 11:21:54,834 [-threads-1977564438)] [ STANDARD] [ your_ruleset:02.10.99] (com.pega.pegarules.search.internal.es.AbstractIndexer) WARN your_operatorid - Failed to index entry in batch: UnavailableShardsException[[rule][0] [2] shardIt, [0] active : Timeout waiting for [1m], request: [email protected]]


Steps to Reproduce

  1. Install Pega 7.1.9
  2. Start reindexing


Root Cause



There is an issue with the configuration of the Search functionality. This error is indicating that the Elastic Search is expecting to find existing indexing files but did not find the expected files.
("Shards" is the internal name which Elastic Search uses to describe the various files which hold pieces of the index.)

The exception can be either that the indexing files have been corrupted, they are not present where expected, or the file system does not have sufficient space for the intermediate used by the indexing process.

The following information should be checked and validated:

Is the PegaRULES Node Information correct?
Is the value on the SMA landing page for this jvm the same value as the Seacrh Index Host Node Setting on the System > Settings > Search landing page?

Does the indexing directory have sufficient space for the index?
Run a directory list for the indexing/explicitindexdir and review the amount of available space.
This setting can be seen on SMA > Administration > Configuration Management.
For a reindex operation, Elastic Search may require two or three times the amount of space as the finished indexes to hold the temporary files used to optimize the indexes.



Resolution



Clearing the explicit index directory, causing the Reindex operation to recreate the index files, allowed the Reindex operation to complete successfully. 
Suggest Edit

Published September 23, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us