Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Schedulers are not initialized as intended in a clustered environment

Written By

Richárd Szabácsik

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • In a clustered environment if we restart the nodes at the same time for a deployment, schedulers and information can be lost. 

Environment

  • Liferay DXP 7.3

Resolution

  • The issue described above is caused by not starting clustered nodes sequentially which is considered to be a bad practice.
  • With the non-sequential restart we introduce a race condition to our system. If one of the nodes with a previous 'slave' status gets elected as a 'master' that node will not have the information we initialized before, therefore it will be lost.

  • In general for DXP it is a requirement to start the nodes sequentially. This means that you need to wait until a node fully starts up, before starting the second one.

Additional information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?