Symptom
This article is specifically targeted towards cluster related problems that happen with a custom configuration, e.g.
cluster.broadcast.method.jgroups.configuration=custom-jgroups-tcp.xml |
- After making this change, you may notice that pods are dropping out of the cluster more often and not rejoining. In hac > Monitoring > Cluster, not all pods will be listed and you may even find inconsistent results depending on which backoffice pod you are looking from.
- In the logs, you will find more errors of the form: "WARN","loggerName":"org.jgroups.protocols.TCP","message":"JGRP000032: hybrisnode-24: no physical address for hybrisnode-19, dropping message"
- Still in the logs, you might also find errors such as: "WARN","loggerName":"org.jgroups.protocols.pbcast.GMS","message":"hybrisnode-31: too many JOIN attempts (10): becoming singleton"
- If you manage to catch the issue in real time and run probe as per 2507555 - How to use JGroups Probe to diagnose hybris cluster issues, you will notice that one or more pods have different coordinators and belong to a different cluster island than the rest of the pods.
- When logging in to hac and navigating to Platform > System > System properties tab, you do not find the properties below:
hybris.jgroups.remove_all_data_on_view_change
hybris.jgroups.write_data_on_find
Read more...
Environment
SAP Commerce Cloud for versions below:
- 1905 on patch level 6 or greater.
- Any major version after 1905 (e.g. 2005, 2011, etc.) on any patch level.
Product
SAP Commerce Cloud all versions
Keywords
cluster,jgroups,view,coordinator,jgroupsping , KBA , CEC-SCC-CLA-ENV-EMG , Environment Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.