OFFHEAP_VALUES ignoring max memory limit

Hi, Can you confirm why ignite logs this warning for caches configured in OFFHEAP_VALUES MODE, whereas documentation suggest it support max memory parameter in this mode. Warning in logs. Off heap maximum memory configuration property will be ignored for the cache working in OFFHEAP_VALUES

Segmentation policy.

Hi, can you please confirm on segmentation policy. We have configured Restart policy and I see this in logs. however, grid did not restart, rather it went in segmentation. We have our custom script to restart java process (Ignite node). 2016-09-09 12:14:26.162 BST [WARN] -

Remote node gc pause

Hi, We see following error in our grid quite frequently. 2016-09-09 09:36:12.458 BST [WARN] - thread="tcp-disco-msg-worker-#2%MMEventOrchestratorGrid%" - class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi" - Timed out waiting for message to be read (most probably, the reason is in long

Re: "OFFHEAP_VALUES" MODE (VISOR CONSOLE)

Thanks Val. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/OFFHEAP-VALUES-MODE-VISOR-CONSOLE-tp7601p7631.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

"OFFHEAP_VALUES" MODE (VISOR CONSOLE)

Hi, We have configured few caches in "OFFHEAP_VALUES" mode and trying to see how entries are being deployed (ON/OFF) using visor. Our observation it that for "OFFHEAP_TIERED", visor show entries in off heap metrics on visor console. However, for OFFHEAP_VALUES, visor show count 0 for off heap and

Runtime error caught during grid runnable execution

Hi, We tried to do a resiliency test for 7 node grid (where in 2 nodes as cache servers replicated mode). Whereas failover was transparent from one node to other node, however, on trying to reconnect first node back, we got following error and java process seems up after that, however, it is not

Re: Failed to wait for initial partition map exchange

Jason Scenario that you shared is same as ours and we face similar issue for large heap servers grid where one of node in restart keeps waiting on initial partition map exchange. Have you received a fix or were able to hack a solution. Please share. Thanks. -- View this message in context:

Note that large topology

Hi, We get following warning when we restart a client node trying to connect a grid of 7 servers. '2016-09-05 13:39:00 [WARN] [Thread=main] [class=org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] Node has not been connected to topology and will repeat join process. Check remote nodes logs