1. Home
  2. Portal
  3. RE: Cluster Setup using Replicated DB instead of Clustered DB -Asset Pub Is

RE: Cluster Setup using Replicated DB instead of Clustered DB -Asset Pub Is

Xue Rui Loh, modified 4 Years ago.
Cluster Setup using Replicated DB instead of Clustered DB -Asset Pub Issue?
New Member Post: 1 Join Date: 10/12/20 Recent Posts
Hi everyone,My team is currently running a setup where we have:
  • A Liferay Cluster consisting of - 2 Production App Servers and 1 DR App Server
  • A Database Cluster (3 MySQL Nodes) serving Production App Servers
  • A Replicated Database serving the DR App Server
Edits/Creations in Prod are updated to DR with no issues (like hot-hot config). Web content/pages created in Prod appear in DR (in admin or actual URL pages).However in DR, the Pages with Asset Publisher does not update. The only way for the DR's Asset Publisher to show the asset created in Prod is to republish it in DR. After republishing in DR, any changes in the new asset's title from any side would reflect in the other.
We've tried reindexing (only removes deleted entries, never updating new entries), restarting, refreshing the caches, etc. But still am unable to get the asset publishers updated. We're still unsure of the cause - the database might be the point of difference, but we've compared the DB and it sees like they're the same (despite using replication and not clustered).
Anyone has any experience with this setup and any workarounds to get the Asset Publisher in DR working?
(Note: Same thing happens if the update/creation was done in DR, Prod's Asset Publisher does not update with it.)
thumbnail
Olaf Kock, modified 4 Years ago.
RE: Cluster Setup using Replicated DB instead of Clustered DB -Asset Pub Is
Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts
Xue Rui Loh:

We're still unsure of the cause - the database might be the point of difference, but we've compared the DB and it sees like they're the same (despite using replication and not clustered).
Anyone has any experience with this setup and any workarounds to get the Asset Publisher in DR working?

Asset Publisher filters through use of the full-text-index, e.g. Elasticsearch (assuming you're on a current version). If you have replicated the index as well instead of creating an ES cluster, you'll have to make sure that the other location updates the index after the database replication has been done, not before.
Plus, so that documents are available everywhere: Did you replicate your Document Library as well? There's a lot more than just the database to take care of when clustering. And if you go through a nonstandard way, you better know exactly what you're doing...