Hi Val, sorry for this late reply. yes, we have a client node constantly joining and leaving topology. does the new versions of Ignite have improvement on this issue?
the reason client node constantly joining and leaving topology is twofold: 1. we used a visor cli called by cron job to check there should be more than 2 server nodes, it send out an email alert otherwise. it runs every 10 minutes. it collects the server count like this: IGNITE_COUNT=`/usr/local/apache-ignite-fabric-1.6.0-bin/bin/ignitevisorcmd.sh -e="'open -cpath=/usr/local/apache-ignite-fabric-1.6.0-bin/config/default-config.xml;node;c'" |grep -e "Server " |wc -l` 2. we have another cron job to do some cleanup for the application, which also connects to the topology and leave after done, also runs every few minutes. many thanks Tom -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14370.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
