Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

The jgroupsping entries not getting deleted from table in Kubernetes environment

Written By

Dávid Hegedüs

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

  • In case of using Kubernetes, you might encounter a problem in your cluster using JDBC_PING, as the entries from the jgroupsping table related to the shutdown pods are not getting deleted.

Environment

  • DXP 7.3+
  • Kubernetes

Resolution

  • Set the following property:
    remove_all_data_on_view_change="true"

Additional Information

  • This property is originally for FILE_PING, but it works with JDBC_PING as well
  • Please note that clear_table_on_view_change is no longer applicable
  • Also, you might want to revisit your grace periods in your Kubernetes settings to make sure that the pods are getting shutdown gracefully

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?