Contents
OPS0010
Issue
After migrating from embedded Elasticsearch to Search and Reporting Service (SRS), the system triggers OPS0010 alert.
The following exception is printed in PDC when this alert is triggered:
[Checking cluster state failed. Reason: FTS is not initialized.][STACK][com.pega.pegarules.priv.search.nextgen.FTSNotInitializedException: Initialization of full text search is either in progress or has failed on this node. Please check the logs if search initialization is complete.
Explanation
The OPS0010 alert is triggered when Full Text Search (FTS) is not initialized. This alert typically arises because the embedded Elasticsearch stops in the environment.
Workaround
Restart the Util nodes (or Search nodes) after the SRS migration is completed (or finished).
OPS0013
Issue
After migrating from embedded Elasticsearch to Search and Reporting Service (SRS), the system triggers OPS0013 alert due to Elasticsearch cluster’s health-related issues.
The following are some exceptions that are printed in PDC, when OPS0013 alert is triggered:
• Elasticsearch index nodes are offline.
• Elasticsearch work index is unstable with index status Incomplete.
Explanation
Pega PlatformTM periodically sends the state and size of the Elasticsearch work index. PDC analyzes this information and verifies whether the pattern is correct.
When PDC generates OPS0013 alert due to the instability of embedded Elasticsearch, a corresponding ElasticsearchFailure case is also created for each application server affected.
PDC recognizes the following causes of instability in the Elasticsearch work index:
• Documents are not available.
• The number of indexed documents is 0.
• The document count may be changed by more than 90% compared to earlier counts.
For more information, refer to OPS0013: Elasticsearch stability issues
This alert can also be triggered after you migrate to SRS.
Workaround
Restart the Util nodes (or Search nodes) after the SRS migration is completed (or finished).
PEGA0137
Issue
After migrating to SRS when the items that are ready to be processed are not picked up by pyFTSIncrementalIndexer QP, Pega Platform generates the PEGA0137 alert.
Explanation
The OPS0137 alert is triggered when ready-to-process items are left in pyFTSIncrementalIndexer QP and the QP is in not running status.
Workaround
Remove the ready-to-process items from pyFTSIncrementalIndexer QP.
For more information, see Remove items in "Ready to process" from Queue Processor
Environment
These alerts can be triggered in Pega Platform 8.x to 24.1 environments.
For more information, see Using full-text search based in Elasticsearch