Old Hazelcast libraries remain after DX NetOps topology upgrade

Products

• Network Observability
• Topology

Issue/Introduction

After performing an upgrade to DX NetOps Topology 25.4.8, older version library files (e.g., 25.4.1-RELEASE) may remain in the Hazelcast library directory.

This is often discovered during file audits or while troubleshooting other performance issues like memory leaks.

Environment

• DX NetOps Topology 25.4.9 and lower
• Directory: /opt/NetOps/netops-topology/hazelcast-5.4.0-slim/lib

Cause

Symptoms: A file listing of the Hazelcast library directory shows multiple versions of the same JAR files:

text

 

graph-store-sdk-25.4.1-RELEASE.jar
hazelcast-persistence-25.4.1-RELEASE.jar
ifm-common-25.4.1-RELEASE.jar

Cause: A flaw in the upgrade playbook fails to overwrite or delete older libraries during the upgrade process.

Resolution

Resolution: Fixed in release 25.4.10 and higher. See Download Broadcom products and software for steps to download this release.

Workaround for versions 25.4.9 and lower:

1. Navigate to /opt/NetOps/netops-topology/hazelcast-5.4.0-slim/lib.
2. Delete the older 25.4.1-RELEASE JAR files if newer versions are present.
3. If newer versions are missing, copy them from a clean installation of the same version.
4. Restart the topology services or reboot the host to ensure changes take effect.

Additional Information

This will only be seen in upgrades, a fresh install of topology will include the correct libraries

 

This is fixed in 25.4.10+