Message Boards

Liferay clustering ( liferay 7.0 ga7)

ashu mohd, modified 3 Years ago.

Liferay clustering ( liferay 7.0 ga7)

New Member Posts: 4 Join Date: 10/21/19 Recent Posts

Hi Team.

Actuall we are trying to do liferay clustering in liferay7.0 GA7 

we are done setup of 2 nodes of liferay ga7 

Node 1 DB pointed to Node2 and restarted both the servers, servers got restarted properly and able to access the portal

And also done setup with NFS Advance file system in Node3 , But when i mount the file system in Node1 at /data/document_library

And i added the below property in portal-ext.properties

## dl.store.impl=com.liferay.portal.store.file.system.AdvancedFileSystemStore

I cound not able to see the files in document_library directory 

And also getting error like

2021-01-18 12:28:22.162 ERROR [http-nio-8080-exec-1][PDFProcessorImpl:164] java.lang.IllegalStateException: Store is not available
java.lang.IllegalStateException: Store is not available

Warm Regards.

thumbnail
Olaf Kock, modified 2 Years ago.

RE: Liferay clustering ( liferay 7.0 ga7) (Answer)

Liferay Legend Posts: 6403 Join Date: 9/23/08 Recent Posts

Liferay 7.0 CE was the version where clustering was not built in, you'll have to compile/install an additional module to make it cluster aware. It's available and you can find documentation if you google for it - my recommendation though is to invest the time rather in upgrade than in compiling this extra module: We're now at 7.3, you can't really expect any bugfix and will fall back more and more.

Also note that clustering involves more than just pointing multiple servers to the same database and file system. It's well documented what you'll need to do - those are approximately 7 steps and I'll recommend to go strictly by the documentation.

What you describe ("can't see the documents") most likely is a cache issue - e.g. when you restart, and/or reindex, they probably appear. This is a symptom of missing steps in clustering setup. And to go through all of the steps you'll need to first make your server cluster-aware, either by compiling and deploying the cluster module, or by upgrading.

The path of least resistance is the upgrade.