-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.1 CE GA2, 6.2.10 EE GA1, 6.2.X EE, 7.0.0 M3
-
Fix Version/s: 6.2.4 CE GA5, 6.2.X EE, 7.0.0 M2
-
Component/s: ~[Archived] WCM > Publication
-
Labels:
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:20
-
Fix Priority:4
-
Git Pull Request:
Steps to reproduce:
- Create an structure.
- Create a template linked to that structure.
- Create for example 3000 web contents with 30 versions (9000 journal articles in total) per each one using that structure.
- Go to manage structures, open the structure previously created and save.
It will take a long time to save the structure (even hours)
TECHNICAL NOTE
The reason for the bad performance is that any time we save a structure we reindex the articles related to it, so 9000 indexations in total. However there is a bug whereby when we are going to index a journal article version we take all its versions so, for the last example, we perform 30 * 30 = 900 indexations per web content so, 900 * 3000 = 2.700.000 indexations in total.
WORKAROUND
The following issue mitigates the problem:
https://issues.liferay.com/browse/LPS-48407
- causes
-
LPS-51880 After modifying a Structure, a wrong webcontent version is indexed in Lucene index when journal.articles.index.all.versions=false
- Closed
- depends on
-
LPS-47829 Exceptions when deleting a user groups and organizations
- Closed
- is duplicated by
-
LPS-50586 Low perfomance for saving an structure if it's related to a lot of contents with several versions
- Closed