Hi Andrew, Thanks for the reply. Here is the configuration that I use for the cluster. Because we have are maintaining 3 data copies in the cluster, if data loading from node is failed then it should be able to get the data from other node. isn't it?
Thanks in advance for your support Raja <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <bean id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration"> <property name="clientMode" value="false"/> <property name="peerClassLoadingEnabled" value="true"/> <property name="metricsLogFrequency" value="0"/> <property name="gridLogger"> <bean class="org.apache.ignite.logger.log4j.Log4JLogger"> <constructor-arg type="java.lang.String" value="ignite-log4j.xml"/> </bean> </property> <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="ipFinder"> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder"> <property name="multicastGroup" value="228.10.10.157"/> <property name="addresses"> <list> list of static IPs </list> </property> </bean> </property> </bean> </property> <property name="communicationSpi"> <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> <property name="socketWriteTimeout" value="10000"/> <property name="messageQueueLimit" value="10240"/> </bean> </property> <property name="cacheConfiguration"> <list> <bean class="org.apache.ignite.configuration.CacheConfiguration"> <property name="atomicityMode" value="ATOMIC"/> <property name="backups" value="3"/> </bean> </list> </property> </bean> </beans> -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Local-node-SEGMENTED-Data-Lost-on-a-Partitioned-Cache-with-backups-of-3-tp11683p11689.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
