Hi Evgenii, Thank you very much for your help. it is reduced to 5 mins now. I believe, we should have some documentation on partition count as per the data size.
Currently Ignite is showing my native persistence size around 800 MB, so can I still decrease the partition count to improve the startup of the ignite cluster. following is metric ^-- Node [id=5624a0e4, uptime=2 days, 00:40:03.756] ^-- H/N/C [hosts=3, nodes=3, CPUs=24] ^-- CPU [cur=6.03%, avg=5.48%, GC=0.03%] ^-- PageMemory [pages=187791] ^-- Heap [used=533MB, free=82.63%, comm=3072MB] ^-- Off-heap [used=742MB, free=43.95%, comm=1324MB] ^-- sysMemPlc region [used=0MB, free=99.99%, comm=100MB] ^-- default region [used=741MB, free=27.57%, comm=1024MB] ^-- metastoreMemPlc region [used=0MB, free=99.56%, comm=100MB] ^-- TxLog region [used=0MB, free=100%, comm=100MB] ^-- Ignite persistence [used=777MB] ^-- sysMemPlc region [used=0MB] ^-- default region [used=777MB] ^-- metastoreMemPlc region [used=unknown] ^-- TxLog region [used=0MB] ^-- Outbound messages queue [size=0] ^-- Public thread pool [active=0, idle=0, qSize=0] ^-- System thread pool [active=0, idle=6, qSize=0] 2) We are receiving an exception "Failed to map keys for cache (all partition nodes left the grid) " when 2 nodes left and one is running. So please could you help me with this error as well. I have created new topic for it. http://apache-ignite-users.70518.x6.nabble.com/Failed-to-map-keys-for-cache-all-partition-nodes-left-the-grid-tt25964.html Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/