How to use JDBC ping for DXP 7.1 dockerized cluster in Kubernetes
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
- We have a 7.1 cluster in Kubernetes with docker image Liferay nodes. We don't know in advance what IP address would be assigned to Liferay containers.
- As the pods can get killed and then the cleanup does not happen, the JDBC ping may not be an option.
Environment
- Liferay DXP 7.1 cluster docker images / deployed and managed by Kubernetes
Resolution
- Set clear_table_on_view_change to true in the JDBC_PING tag of jdbc_ping_config.xml of each cluster node, for the automatic removal of the DB table entries for members which crashed but weren’t removed for some reason.
- Please find more in the jgroups documentation.
Did this article resolve your issue ?
