Re: Ignite loadCache performance issue

Denis Hi, I have already did and it worked. Also the bottleneck about performance is probably db related. Thx so much for help -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how to create Index for binary or byte type value

Hi Val, Would indices be possible on binary data value , I dont think so. I think I will stick with the POJO for now. I have queries on indices and l am not relying on external persistence system. a) What are the different indices type Ignite supports apart from equality i.e does it support the

Re: how to create Index for binary or byte type value

Rajesh, This actually sounds exactly like binary format Ignite uses to store the data: https://apacheignite.readme.io/docs/binary-marshaller Doing this manually (i.e. explicitly saving some byte array and creating indexes over this array) would not be possible, but I don't think you really need

Re: how to create Index for binary or byte type value

Yes, correct object is stored as byte array As my attribute name is not fixed. I want to have index on different attributes which is not directly visible as the pojo instance variable Rajesh On 19 Jan 2018 3:56 a.m., "vkulichenko" wrote: > Hi Rajesh, > > It's not

Long activation times with Ignite persistence enabled

Hello, I'm wondering if there is a way to improve the startup time of Ignite node when the persistence is enabled? It seems the time is proportional to the size (and number) of the partition files. This is somewhat surprising as I expected the startup time be the same (plus-minus some

Re: Invoke Cache.loadCache method in configuration file?

Yeah, LifeCycleBean is what exactly what I'm looking for, the solution is brilliant, thank you. package com.debug; public class CustomizedLifeCycleBean implements LifecycleBean{ @Override public void

Re: how to create Index for binary or byte type value

Hi Rajesh, It's not clear what you're trying to achieve. So are you going to store the attributes as a map or in serialized form as a byte array? And what exactly should be indexed? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Invoke Cache.loadCache method in configuration file?

No, you have to call loadCache explicitly in your code. If you want to do this on startup, you can try utilizing a lifecycle bean: https://apacheignite.readme.io/docs/ignite-life-cycle. Although keep in mind that you need to make sure that all nodes are started before you start loading. -Val

Re: Node fails to recover

Yeah, that is wha I thought. But Ignite is wired with Spring so that would mean restarting the whole ApplicationContext. Ralph > On Jan 18, 2018, at 10:37 AM, ilya.kasnacheev > wrote: > > Hello Ralph! > > I imagine if your Ignite is running inside a web container,

Invoke Cache.loadCache method in configuration file?

Hi, I'm testing the persist store function, it works correctly, but I had to call the loadCache function manually in a Java app. can I realize this in configuration file? this way might save a lot of time. Thank you. http://www..>

Re: Node fails to recover

Hello Ralph! I imagine if your Ignite is running inside a web container, it is the responsibility of your code to check its status and when it disconnects, notify balancer that current node can't handle requests and then try to re-join topology with a new instance of Ignite. Regards, -- Sent

Re: Remote client

Hello, Alexey. Thank you. I realy have public ip in client. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node fails to recover

Also, I suppose another option would be to handle the event by telling our load balancer to take the node out of the cluster but then have Ignite reattempt to reconnect, but I have no idea how I could tell Ignite how to do that. Ralph > On Jan 18, 2018, at 9:10 AM, Ralph Goers

Re: Node fails to recover

Thanks for the info. JVM_RESTART won’t work for us because this a web application running in Tomcat using Ignite for a distributed cache. JVM_RESTART is documented as only working in a command line application. The problem we experienced was bad since our load balancer didn’t realize one of

how to create Index for binary or byte type value

Hi All, The problem statement is in context of "In-Memory Data Grid" persistence enabled. I have requirement/limitation to store the value of a class's object as byte [] , understood by the application in certain format. IgniteCache cache =

Re: Remote client

Hi, Does your remote client has public IP? Please note that client node should be accessible for TCP incoming connections from a server node, i.e. the server node should be able to connect to client IP as well. Your client IP is 192.168.8.132. And your server node is not able to connect it. So

Re: usage of Apache ignite as Key value DB

Hi Mikael, Thanks a lot for your response, got a fair understanding of this. Have some queries on Indexes , starting a new thread for this. Thanks, Rajesh On Wed, Jan 17, 2018 at 6:33 PM, Mikael wrote: > There are a number of ways do to persistence for the cache,

Re: Integration with Hibernate 5.2.X for L2 Cache?

Hi, Hibernate 5.2.x requires java 8, while ignite requires java 7. AFAIK, we are going to drop java 7 in upcoming ignite-2.4 version. So, it will be possible to add Hibernate 5.2+ support in next 2.5 version. Feel free to create a ticket. On Thu, Jan 18, 2018 at 1:45 PM, SirSpart

Re: Node fails to recover

Hello! Maybe it's network problems and not full GC. As you can see from logs there's failure to acknowledge a discovery message. As for "re-discovery" - as far as my understanding goes, that't not how Ignite works. Client nodes will indeed try to re-discover server, but server nodes consider

Re: Re: Nodes can not join the cluster after reboot

Aaron, could you share code of com.tophold.trade.ignite.service.CommandRemoteService ? Thanks, Evgenii 2018-01-18 16:43 GMT+03:00 Evgenii Zhuravlev : > Hi Aaron, > > I think that the main problem is here: > > GridServiceProcessor - Error when executing service: null >

Re: Re: Nodes can not join the cluster after reboot

Hi Aaron, I think that the main problem is here: GridServiceProcessor - Error when executing service: null diagnostic - Pending transactions: [WARN ] 2018-01-17 10:55:19.632 [exchange-worker-#97%PortfolioEventIgnite%] [ig] diagnostic - >>> [txVer=AffinityTopologyVersion [topVer=15,

Re: Cannot insert data into table using JDBC

Thanks a lot. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Logic of work Ignite cache

Alex, > So, as I understand, if Ignite don't find data in cache (hot cache, RAM) , then it tried to find it in persistent cache? Am I right? Yes, it can work this way. If you enable native persistence, then it will work this way out-of-the-box. If you choose to use 3rd party persistence, then,

Re: Logic of work Ignite cache

Denis Mekhanikov wrote > I'm not sure, what you mean by "some data providers". Thanks. "some data providers " - there are some external services for our data. This mean that we execute on server nodes some tasks and if we don't find results of our search in cache, we send requests to these "data

Re: Data lost when primary nodes down.

Hi! You didn't configure any backups for your cache, so, there is only one node for every key in the cluster. In order to configure backups for cache, use CacheConfiguration.setBackups(int)

Re: Logic of work Ignite cache

Hi Alex! There are a few ways, how you can introduce persistent data layer. First of which is native persistence: https://apacheignite.readme.io/docs/distributed-persistent-store It will store data on disk, and guarantee, that it will be available after nodes are restarted. Also it implies, that

Re: Ignite loadCache performance issue

Hasan, Unfortunately, there is no way to disable off-heap memory. Since Ignite 2.0 Ignite operates over memory pages, that are allocated in off-heap memory, and accessed over Java Unsafe. You can configure eviction policy in terms of occupied memory though. You can say, that when there is a

Re: Integration with Hibernate 5.2.X for L2 Cache?

Nobody answered? Guess i'll answer myself. Long story short: Not yet. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Remote client

When the client connects to the server on the local network everything works fine, when the client connects to a remote server receive this log: Server: Info: Pinging node: c129d9da-dbeb-4c75-9120-a8c463ae7d72 Info: Finished node ping [nodeId=c129d9da-dbeb-4c75-9120-a8c463ae7d72,

Logic of work Ignite cache

Hello all. Sorry, perhaps, for newbie question.Can you consult me about logic of work Ignite. We use some app. It send some searchkey to Ignite and get search results. We use Ignite 2.0. So we have scheme App <->Ignite <->Persistanse cache via MySQL for Ignite <-> some data providers. Am I right