ignite persistence size growing

Hi Team, I have enabled persistence with cache eviction of 8 days of creation time. But my persistence data folder is keep on growing. Even we are deleting entries from Caches, but persistence size still growing. Is there way we can clean and reduce the size of persistence. Thanks & Regards,

CacheJdbcBlobStore loadCache (Hot loading data into cache)

Hi Team, I am using Apache Ignite 2.7 It seems to be hot loading is not available for CacheJdbcBlobStore using loadCache. I have tried multiple times and but nothing is working. When I looked into implementation it is extending CacheStoreAdapter and it got empty implementation. So please let me

Re: Failed to map keys for cache (all partition nodes left the grid)

Hi, I want to receive the data even on one node. Can I add any set of commands so that it can copy all partitions to active nodes when node left (OR) Can I make it is cache mode replicated and will it work? Thanks & Regards, Venkat -- Sent from:

Re: Ignite startu is very slow

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

Failed to map keys for cache (all partition nodes left the grid)

Hi Team, I have 3 node server mode cluster setup with Cache mode Partitioned with 1 backup. We are receiving above error as soon as 2 nodes left from cluster. All 3 nodes are on baselinetopology. Collection baselineNodes = ignite.cluster().currentBaselineTopology();

Re: Ignite startu is very slow

Hi, Sorry to bother you. All Data in Ignite native persistence, so please could you guide me how to reload the data again. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startu is very slow

hi Team, any update or clue on above issue. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startu is very slow

Hi ezhuravlev, I have waited for more than 2 hours and captured the logs. please find attached log in the post. nodeStartup.log . Please could you provide me the guidance to fix it. Thanks & Regards, Venkat -- Sent

Re: Ignite startu is very slow

Hi, This time it is got hung. so I have killed the nodes and restarted again. Please find attached logs on startup. node1.log node2.log As you

Re: Ignite startu is very slow

Hi, Please find attached log. ignite_deactivate.log whole cluster is de-activated and it is going in hung state. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startu is very slow

Hi, I have deActivated the cluster and closed, but still same issue persists. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startu is very slow

Heap size is 3 GB. And MaxDirectMemorySize is 1.5 GB. My cache size is around 2 GB and on Disk around 5-6 GB maximum. My total cache elements are around 50-60 thousands. I will receive around 700-800 thousand messages for a day and I will update that in cache. So please could you let me know

Re: Ignite startu is very slow

Please help. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startup is very slow

Hi Team, any update on above ticket. any hints to investigate further. As per me, it seems to be Partition Map exchange. But I am unable to understand why it is taking time on startup. It is got only 3 nodes. I had the ran the SAR command as well, it was showing iowait as 6-10%. Even it is

Re: Ignite startup is very slow

Hi Team, Please could any body help me or guide me to solve this issues. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite startu is very slow

No, As you can see in the configuration it is ATOMIC mode. I did not write any transactional code, just get and put and scanQuery. Native persistence is enabled. Most of the writes done by one node and other 2 nodes mostly read and less write. It is got only 3 nodes. each node is 4 CPU and 8

Ignite startu is very slow

Hi Team, I am using Snapshot version of 2.7(Ignite ver. 2.7.0.20180806#19700101-sha1:DEV). Startup time is having between 8-30 mins. My complete data set also very small, it is around 3 GB to 4 GB on Disk. Please find attached logs and configuration in it. example-ignite.xml

Re: ScanQuery failing on Client Mode

Hi, it is available. I can call other methods in the same service. Cache.query is working in server nodes, but not on client nodes. But ARCacheDelegateImpl is not available in server node. will it causing the issue?. One more questions, Can we run the few server nodes with persistence and few

ScanQuery failing on Client Mode

Hi Team, ScanQuery is failing on ClientMode. below is the error. ARCacheDelegateImpl is my service class and it is available in my classpath as well. [err] javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Query execution failed: GridCacheQueryBean

Re: Too Many open files (native persistence bin files)

one correction: lsof showing the information for threads as well, so that is why it is showing number of Threads * file descriptor. My current ulimit is 32635, open files in 6000 but still we are receiving too many files open. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Too Many open files (native persistence bin files)

Hi Team, We have got one production issue using Ignite. as per the lsof (File descriptors ) it is around a 1 million open files with given process and all used by ignite. I am running ignite as emebedding into my web application with native persistence enabled with 3 nodes as Cache Replicated

Re: Failed to add node to topology because it has the same hash code for partitioned affinity as one of existing nodes

Hi It is having unique consistentId across cluster. All nodes running for some time, it is happening after some time.Please see the discoverySpi and consistenId details below. *Node1 ConsistentId (Server 1):*

Failed to add node to topology because it has the same hash code for partitioned affinity as one of existing nodes

Hi Team, I have configured my all caches replicated mode with native persistence enable and running it on 3 nodes. 2 nodes runs on same server and another node run on different server. I have configured unique consistentId for each node and unique IGNITE_HOME. I also configured

Re: SYSTEM_WORKER_TERMINATION (Item Not found)

Hi, It seems be all of them resolved. Can I go head and download nightly build and use it. Or will it have any impact. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

SYSTEM_WORKER_TERMINATION (Item Not found)

Hi, We are still receiving Runtime Failure bound (Item not found) in 2.6 as well. We are receiving this error everyday midnight check point. We have around 15 caches and configure expiry as 3 days, 8 days and 2 caches are eternal. Please find attached checkpoint log and error in below links.

Re: Runtime failure on bounds

Hi, We have received Runtime failure on bounds again in 2 days. I am using ignite 2.6 and started all nodes from scratch ( removed existing data). error below [7/21/18 13:22:43:031 UTC] 008f E Critical system error detected.

Re: Runtime failure on bounds

Hi Andrei, Yes, I have stopped all the servers and removed corrupted nodes data and upgraded to 2.6 and restart the server. any more suggestion and configuration changes to prevent this issue. Thanks & Regards, Venkat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Runtime failure on bounds

Hi Team, We are receiving Runtime failure on bounds even after updating it to 2.6 version. We used to receive Failed to get page IO instance (page content is corrupted) from 2.3, 2.4 and 2.5, now in 2.6 it is changed to Item not found: 1. Till now we are in test environments but we are

Re: Node stopped automatically

Please could you provide some pointers, so that I can look deeper into the issue. 1) Does PageMemory cause any issues as per the metrics, one node is contains only 70 and other node is PageMemory [pages=390178] 2) Why whole cluster is going down, when one node is down 3) Can I restart the

Re: Node stopped automatically

Ignite related only that log, After that only cache stopped exception in the log. Even we have enabled -DIGNITE_QUIET=false, but it is printing that much only. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Node stopped automatically

Hi, Node stopped automatically after 48 hours uptime. Please find the logs below. I got 2 hosts and 3 Ignite nodes Host 1, Node 1 Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=5582ed60, uptime=48:00:04.981] ^-- H/N/C [hosts=2, nodes=3, CPUs=4]

Re: ClusterTopologyServerNotFoundException

Hi, Thank you very much. We are receiving this error only when one node was running. Exception is gone as soon other nodes are started and joined the cluster. I have attached the single node where we received the error. exception.log

Re: Cache is too slow

Hi, Thank you very much for your reply. I found that it is an issue with Webserver. I can see now Ignite cache is giving results are around 1-millisecond to 14 milliseconds with onheapEnabled and without onheapEnabled, results are around 3 milliseconds to 200 milliseconds. Are these expected

Cache is too slow

Hi,We have setup 3 node cluster with Replicated caches. Ignite starts with our JAX-RS servvices on Liberty server.We have exposed an API and reading the values from cache(no business logic). Just read it from Ignite cache and return it and it is taking more than 6 seconds. We had run load test

ClusterTopologyServerNotFoundException

Hi,We have setup 3 node cluster on Linux server with 2 core CPU and 8 GB RAM. We have configured Ignite persistence and replicated caches.Please find attached configuration in the email. example-ignite-sample.xml

Delete Message Topic and Listener

I have setup ignite cluster with native persistence. I enabled messaging and created a message topic and added listener to it and deployed. There were some business logic errors in the listener code and I fixed it. But the changes are not yet all reflecting. I have tried restarting the ignite