Type: Regression Bug
Affects Version/s: 6.2.3 CE GA4, 6.2.10 EE GA1, 6.2.X EE
STEPS TO REPRODUCE
1.- Set up a cluster of Liferay with two nodes, in ports 8080 and 9080 for HTTP connector for example.
The following properties can be used, for node 1:
For node 2:
2.- Include the following lines in WEB-INF/classes/log4j.properties:
3.- Start only node 2 and instance an Asset Publisher in the front page.
4.- Create lots of documents and contents unitl you get a index of some GB (I used a 3 GB index)
5.- Start node 1, and access the Front Page. If it was started before, delete the lucene directories before starting this node.
The index dump takes several minutes and hangs the rests of requests to the server (none of them gets a response, locking out the HTTP thread pool)
The following traces appears, showing that it takes more than 30 minutes to process it:
The index dump should be fast enough to avoid locking all the requests to the server
A new property had been included to manage how the index is processed when obtained from other nodes: