Hi!
I have growing java thread count. The application crashes with OOME. The
application is very simple, only reading values in a cache.
Any suggestion to debug this issue?
Ignite 2.4
<>
I think I know what I need to do. I need to override the loadcache method and
implement my own based on the example on the site. I think if I use generics
I could parse in any class and it will handle the load. What's your thoughts
on that?
--
Sent from: http://apache-ignite-users.70518.x6.nabbl
Hello,
Please find below link to SQL documentation :
https://apacheignite-sql.readme.io/docs/overview
You will find answers to most of your queries here.
1. H2 is only used as SQL query parsing engine and for generating execution
plans. Data was/is always stored in Caches.
3. All kind of quer
Hello,
After step 4 above, Ignite will detect that original primary Node A is up,
so all the updates happened while Node A was down will be applied to Node A
so thay it is latest and it will marked as Primary again. Till the time
this process is completed, Node B will still be considered as primar
Hello,
For second question above, you can have listener to listen AFTER_NODE_STOP
event and take action as per your logic (in your case changing BLT).
Regards,
Gaurav
On 14-Sep-2018 9:33 PM, "eugene miretsky" wrote:
Hi,
What are best practices for handling split brain with persistence?
1) D
i have setup rmdbs integration with read-through
if i query an empty cache it should read-through from the underlying system
but that isn't happening i get the following error
[16:43:35,351][SEVERE][client-connector-#56%StoxxDataLake%][JdbcRequestHandler]
Failed to get parameters metadata [reqId=
hi
Initially this will be a single node demo but will be deployed as a 10 node
cluster. I am running 2.6 and it is loading data from SQL server. There are
2 issues i am finding at the moment
1) it takes an hour to load but only loads 2.5k out of 4.6 million records
(this seems serious)
2) it take
