-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.1.X, 7.2.X, Master
-
Fix Version/s: 7.1.10 DXP FP18, 7.1.10.5 SP5, 7.1.X, 7.2.10 DXP FP5, 7.2.10.2 DXP SP2, 7.2.X, 7.3.10 DXP GA1, Master
-
Component/s: Search Infrastructure
-
Branch Version/s:7.2.x, 7.1.x
-
Backported to Branch:Committed
-
Fix Priority:4
-
Sprint:Search|S03 Sprint 14| 4.6-4.27
-
Git Pull Request:
Steps to Reproduce
- Startup Liferay
- Create and deactivate Groups (500,000+) (can use MySQL script)
- Navigate to Control Panel > Users > Users and Organizations
Expected Result
The page would load without too much delay
Actual Result
Even after accounting for the initially slower first page load (as classes initialize), it takes over a minute for the page to load.
[MySQL Script] - Generate 500,000 Inactive Groups
Attached is a sql script that can be used in MySQL to generate 500,000 inactive groups for testing this issue: insert_inactive_groups.sql
Note: The script targets the schema lportal, which can be changed by modifying the first line:
USE lportal;
Change lportal to your target database schema.
- causes
-
LPS-121537 GroupLocalServiceImpl.getGroupIds always retrieves results from database
- Closed
- Is blocked by
-
LPS-112137 junit.framework.AssertionFailedError due to unable to validate fragment entry
- Closed
- relates
-
LPS-121537 GroupLocalServiceImpl.getGroupIds always retrieves results from database
- Closed
-
LPS-122035 Avoid filter ES queries by ActiveGroupIds
- Closed
- Testing discovered
-
LPS-111623 ElasticsearchStatusException "The number of terms exceeded the allowed maximum" (defined in index.max_terms_count) occurs on Elasticsearch 7 when there are more than 65536 inactive groups (users or sites)
- Verified