Are there any known issues in OOTB 7.1.7 search?
Hi ,
We are planning to move to OOTB 7.1.7 search. We are having 15+ work types and nearly 15k cases and adding nearly 100+ cases every day. A bunch of attachments etc etc.
Is there any known issues with 7.1.7 and any suggestions of hotfixes. Just curious of upgrade to 7.1.9 upgrade on why and when. Thanks in advance !
Regards,
Harinath Chakrapani.
***Updated by moderator: Lochan to branch reply and create new post***
Schwab
US
Heard that the search depends on "pr_sys_statusnodes table" and if it gets corrupt we need to trigger the reindexing process that may take couple of hours leading to a P1 issues in production.
Hence very cautious to know how often the indexes in the statusnodes table gets corrupt and why? Any other alternatives other than complete reindexing?
Pegasystems Inc.
US
Elasticsearch is new in 7.1.7 and was a bit unstable (although the performance and power gains from the old Lucene search engine are, IMO, worth it even in 7.1.7). Issues were fixed in later versions, and Elastic Search should be largely stable in 7.2+. There's no hotfixes for this I'm aware of - mostly, this is engine-level stuff included in later versions.
Even in 7.1.7, corruption of the search index is rare - most applications will never see it. The fix if it does happen involves a restart, and activity run, and a reindex - see https://community.pega.com/support/support-articles/search-work-index-file-unavailable-or-corrupted for the full details if this comes up. There's no way around this.
See these links for more detail https://collaborate.pega.com/question/rule-index-file-unavailable-or-corrupted-landing-page .
The best thing to do is to use the most recent version of Pega if at all possible, for this and other fixes/ features. If you do have to use 7.1.7, you probably won't see the corrupted indexing issue, but if you do the information above should help.