One Database and multible liferay installations

[Mohamed Salah Sayed, geändert vor 14 Jahren.]

Hello All,
I am new to liferay and I am wandering if the following deployment scenario is okay:
1- Two legs of application servers, which has a liferay running on them.
2- One instance of web server, that load balance between the two legs.
3- One shared Database between the two application servers.

My question is, is there problems in this configuration specilly in the DB, for example the couner ids, will it be okay that the two application servers will not be confused when increamenting the couter in the db ?

Thanks for support

M.Sayed

[Abhishek Saxena, geändert vor 14 Jahren.]

Hi ,

The architecture you have proposed is fine you will not face any issues.
Its common to have multiple nodes pointing to same DB.

Which version are you on.

[MICHAIL MOUDATSOS, geändert vor 12 Jahren.]

Abhishek Saxena:

The architecture you have proposed is fine you will not face any issues.

Don't you think he should consider disabling User indexing and entity caching?

[Juan Gonzalez P, geändert vor 12 Jahren.]

Nop. You can have multiple nodes and having cache and indexing properly replicated.

For that only have to enable cluster link and index replication.

Please search for "cluster" in user guide/wiki, there is a section for that.

[Hitoshi Ozawa, geändert vor 12 Jahren.]

Beside the indexes, there's also the prefetch counter problem. Setup distributed caching as Juan advised or set the counter.increment=1. If both are active, use the distributed cache. If one of them is a standby, set the counter.increment to 1.

#
# Set the number of increments between database updates to the Counter
# table. Set this value to a higher number for better performance.
#
counter.increment=100