Throughput issues due to the increased number of search write requests after LPS-65978

• Type: Regression Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.X EE, 7.0.0 DXP FP1, 7.0.2 CE GA3, 7.0.0 DXP SP2, Master
• Fix Version/s: 6.2.X EE, 7.0.0 DXP FP18, 7.0.3 CE GA4, 7.0.0 DXP SP4, 7.0.X EE, 7.1.0 CE GA1, 7.1.10 DXP GA1
• Component/s: Performance, Search Infrastructure
• Labels:
  • 62-ee-sp20
  • QA-NA
  • ee-ts
  • liferay-digital-enterprise-70-sp4
  • liferay-fixpack-de-18-7010
  • liferay-fixpack-portal-151-6210
• Branch Version/s:
  7.0.x, 6.2.x
• Backported to Branch:
  Committed
• Story Points: 1.5
• Fix Priority: 4
• Last Working Version:
  7.0.0 DXP GA1
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/49045

There are throughput issues in both search engine and Liferay installation after installing LPS-65978 solution

That LPS increases reindexation requests to elasticsearch/solr/lucene

CPU consumption is also increased: all the Indexer "doReindex" logic is executed but only one field is modified (ratings, viewCount, etc...) so a lot of unnecessary database queries and calculations are done.

---

Solution Notes

Changes introduced in the fix for LPS-65978 (affecting when fields 'ratings' and 'viewCount' get updated in the search index) have been reverted. In addition, these fields will no longer be indexed in the BaseIndexer class for AssetEntry objects as of the next Liferay version.

Why was this change made?

Keeping the Ratings and View Count options in the search index in sync with the database has a negative impact on normal operations due to the significantly increased number of index Write requests causing throughput issues and, therefore, performance degradation.

In addition, the view count is not always up-to-date in the database. This behavior is controlled by the Buffered Increment mechanism. You can find more information about this in the portal.properties file.