Legacy Knowledge Base
Published Sep. 10, 2025

MEMORY_CLUSTERED jobs are running in several nodes

Written By

Mariano Alvaro

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

  • According to traces, or any other monitoring system, MEMORY_CLUSTERED jobs are executed in more than one node.

Environment

  • Liferay DXP 7.0, 7.1, 7.2

Resolution

  • MEMORY_CLUSTERED jobs should only run in master node.
  • Ensure that there's only one master node across the cluster executing the following script on every node:
    import com.liferay.portal.kernel.cluster.*;
    
    out.println("** Master: "+ ClusterMasterExecutorUtil.isMaster());
  • Only one node per cluster should print: ** Master: true
  • If it happens occasionally one of the followings could be the cause:
    • Network problems: If the network is slow or it's loosing some packages the cluster could end in a broken status.
    • CPU saturation:If too high, the node would not be able to answer on time to JGroups heartbeat messages, appearing as departed from the cluster.
  •  If the cluster has never been in a healthy status review the cluster configuration, visibility among nodes (firewall, nodes must use the same network interface,...): Liferay Portal Clustering
Did this article resolve your issue ?

Legacy Knowledge Base