Hi Val,
Thanks for the response.
I am trying to figure out the reason why the node was not able to restart
when the logs suggest it is attempting. I looked for the 'Restarting JVM...'
log in the Ignite code and found it in GridDiscoveryManager$DiscoveryWorker
class (pasted below). As per the logic, the restart(boolean cancel) api from
IgniteEx class should have been invoked and the node should have restarted
but it didn't.
I am starting the server node through the ignite.sh script. Below is the
command line I use to start the ignite server nodes and the process
description of a running server node process.
Is there anything wrong with the way I am starting Ignite nodes? The client
nodes are started differently.
/Command-line (From Ignite installation directory) - /
sudo nohup ./ignite-setup/bin/ignite.sh ignite-config/config.xml >
ignite-process.log 2>&1 &
/Process description (output of ps -aef command)/ -
/bin/java -server -Xms2g -Xmx4g -XX:NewSize=1g -XX:SurvivorRatio=6
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+AlwaysPreTouch
-XX:CMSInitiatingOccupancyFraction=30 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled
-XX:ConcGCThreads=4 -XX:+UseTLAB -XX:+ScavengeBeforeFullGC
-XX:+CMSScavengeBeforeRemark -XX:+DisableExplicitGC
-XX:-HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true
-DIGNITE_QUIET=true
-DIGNITE_SUCCESS_FILE=/u/pserv200075/tango/installation/ignite-setup/work/ignite_success_b413d805-0e58-445f-83e4-5e645d83b55b
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=49113
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-DIGNITE_HOME=/u/pserv200075/tango/installation/ignite-setup
-DIGNITE_PROG_NAME=/u/pserv200075/tango/installation/ignite-setup/bin/ignite.sh
-cp
/u/pserv200075/tango/installation/ignite-setup/libs/*:/u/pserv200075/tango/installation/ignite-setup/libs/ignite-indexing/*:/u/pserv200075/tango/installation/ignite-setup/libs/ignite-spring/*:/u/pserv200075/tango/installation/ignite-setup/libs/ignite-zookeeper/*:/u/pserv200075/tango/installation/ignite-setup/libs/licenses/*
org.apache.ignite.startup.cmdline.CommandLineStartup
/u/pserv200075/tango/installation/ignite-config/config.xml
/Ignite Client Node Cache Configuration - /
On client node, IgniteConfiguration bean is instantiated as a Spring
dependency. The cache is created as follows -
1. Create cache manager -
cacheManager = Caching.getCachingProvider()
.getCacheManager(new
ClassPathResource("config/ignite-cache-context.xml").getURI(), null);
2. Create cache -
CacheConfiguration<Key, Value> cacheConfig = new
CacheConfiguration<Key, Value>();
cacheConfig.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cacheConfig.setCacheMode(CacheMode.PARTITIONED);
cacheConfig.setBackups(1);
cacheConfig.setOnheapCacheEnabled(true);
LruEvictionPolicy<Key, Value> evictionPolicy = new
LruEvictionPolicy<>();
evictionPolicy.setMaxSize(1000);
evictionPolicy.setMaxMemorySize(1000000);
cacheConfig.setEvictionPolicy(evictionPolicy);
cacheConfig.setStatisticsEnabled(statisticsEnabled);
cacheConfig.setRebalanceThrottle(rebalanceThrottle);
cacheManager.createCache(storeDetailsCacheName, cacheConfig);
----------------------------------------------------------------
*FROM IGNITE SOURCE CODE*
----------------------------------------------------------------
GridDiscoveryManager$DiscoveryWorker class -
onSegmentation() {
...
...
case RESTART_JVM:
U.warn(log, "Restarting JVM according to configured
segmentation policy.");
restartJvm();
break;
...
...
}
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
