Hi Andrew,
Below is the grid config
<property name="discoverySpi">
<bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
<property name="addresses">
<list>
<value>10.179.29.135:47500..47509</value>
<value>10.179.29.136:47500..47509</value>
<value>10.179.29.137:47500..47509</value>
</list>
</property>
</bean>
</property>
<property name="heartbeatFrequency" value="2000"/>
<property name="maxMissedHeartbeats" value="5"/>
<property name="reconnectCount" value="100"/>
<property name="networkTimeout" value="10000"/>
<property name="socketTimeout" value="10000"/>
<property name="statisticsPrintFrequency" value="60000"/>
</bean>
</property>
<property name="communicationSpi">
<bean
class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
<property name="slowClientQueueLimit" value="18000"/>
<property name="messageQueueLimit" value="20000"/>
<property name="localPort" value="9090"/>
<property name="connectTimeout" value="5000"/>
<property name="idleConnectionTimeout" value="75000"/>
<property name="sharedMemoryPort" value="-1"/>
</bean>
</property>
I have not tried with less number of clients & increasing the number of
servers. Please suggestion in this regard.
Use case:- All the caches are storing session related data (such as login
session and sso token management) which is created once, updating is not
that frequent but accessing is 50 / 60 times.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175p15186.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
