Gracefully fail when scheduler configuration is different between nodes

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, 7.1.X, Master
• Fix Version/s: 7.0.0 DXP FP61, 7.0.X, 7.1.10 DXP FP3, 7.1.1 CE GA2, 7.1.10.1 SP1, 7.1.X, Master
• Component/s: Fault Tolerance > Clustering Framework
• Labels:
  • liferay-dxp-70-sp10
  • liferay-dxp-71-sp1
  • liferay-fixpack-de-61-7010
  • liferay-fixpack-dxp-3-7110
• Branch Version/s:
  7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Story Points: 2
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/63818

Steps to Reproduce:

1. Node1: Set scheduler.enabled to false and cluster.link.enabled to true.
2. Start Node1
3. Node2: Set scheduler.enabled to true and cluster.link.enabled to true.
4. Start Node2

 

Actual Result:

Node2 starts an endless loop during the memory clustered jobs initialization showing everytime a NullPointerException.

 

Expected Result:

Customer should be warned that the current is not a valid cluster configuration.