BE Cache agents are not able to form cluster when run on different Kubernetes Nodes on AKS
Article ID: KB0075290
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | 5.6.1 |
Description
BE Cache agents are not able to form cluster when run on different Kubernetes Nodes on AKS. There appear to be the issue with the Dockerfile (missing new line i.e. echo) which is causing discover url to be incorrectly added to be-engine.tra, which in turn defaults to tibpgm protocol being used. As Kubernetes Nodes are different subnets, BE Cache agents are not able to communicate each other. They must use Unicast instead of Multicast (tibpgm) Discovery.
Issue/Introduction
BE Cache agents are not able to form cluster when run on different Kubernetes Nodes on AKS
Environment
Cloud
Resolution
In order to have a correctly formatted be-engine.tra inside image, first echo (a new line) in Dockerfile needs to be added as follows :-
===========================
RUN echo >> be-engine.tra \
&& echo "java.property.be.engine.cluster.as.discover.url=%AS_DISCOVER_URL%" >> be-engine.tra \
&& echo "java.property.be.engine.cluster.as.listen.url=%AS_LISTEN_URL%" >> be-engine.tra \
&& echo "java.property.be.engine.cluster.as.remote.listen.url=%AS_REMOTE_LISTEN_URL%" >> be-engine.tra \
&& echo "java.property.com.sun.management.jmxremote.rmi.port=%jmx_port%" >> be-engine.tra
===========================
===========================
RUN echo >> be-engine.tra \
&& echo "java.property.be.engine.cluster.as.discover.url=%AS_DISCOVER_URL%" >> be-engine.tra \
&& echo "java.property.be.engine.cluster.as.listen.url=%AS_LISTEN_URL%" >> be-engine.tra \
&& echo "java.property.be.engine.cluster.as.remote.listen.url=%AS_REMOTE_LISTEN_URL%" >> be-engine.tra \
&& echo "java.property.com.sun.management.jmxremote.rmi.port=%jmx_port%" >> be-engine.tra
===========================
Additional Information
Feedback
Yes
No
Powered by
