RE: Re:

Hi Kasnacheev, The below behavior is occurring randomly after stopping the node. Do we have any resolution apart from deleting metastorage folder? Sent from Mail for Windows 10 From: Ilya Kasnacheev Sent:

Re: Setting Cache Size using Max Records

Yes, user upfront defines a config and the idea indeed is to convert the number of records to total bytes. Followup around this. Given i want to calculate the exact row entry size upfront, even before the data is added. Couple of queries, 1. Is there a way(api) just based on the Cache (table),

Re: Question on Key choice for an Ignite cache

He Eugene, To elaborate on Ilya's answer, you can define a POJO for your key like as follows: public class AccountKey { String email; String phoneNumber; //don't forget to implement equals() and hashCode() so // that Ignite partitions and locates your records properly } and

Re: Question on Key choice for an Ignite cache

On Tue 30 Jun 2020, 13:51 Ilya Kasnacheev, wrote: > Hello! > > You can also use Binary Object (POJO) as a key, i.e., you can use an > Object with String email and String phone fields. > > I don't recommend mangling strings further than concatenation. String key > is no worse than numeric key. >

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

Hi, Looks like the system is being slowed down for some reason. Many Ignite operations are taking a long time(>30 sec) where they should complete much quicker. Are you able to go back to 2.7.6 on the exact same config/setup, run the system for a period of time then go to 2.8.1 and

Blocked system-critical thread has been detected - After upgrade to 2.8.1

Hi! We have been working with Ignite 2.7.6 without incidents, since we upgrade to 2.8.1 (same machine, same resources) we are getting "Blocked system-critical thread", Ignite server nodes stops responding. We have been notice that after several hours (about 8 or 9), it recovers itself, but

Re: How to do address resolution?

Ok so. Is this expected behaviour? From user perspective this seems like a bug. Visor is supposed to be used as a way to monitor... So if as a user we enter a command and it just freezes indefinently it just seems unfriendly. In another thread the the team mentioned that they are working on

Re: Question on Key choice for an Ignite cache

Hello! You can also use Binary Object (POJO) as a key, i.e., you can use an Object with String email and String phone fields. I don't recommend mangling strings further than concatenation. String key is no worse than numeric key. Regards, -- Ilya Kasnacheev вт, 30 июн. 2020 г. в 15:17,

Question on Key choice for an Ignite cache

We would like to create an Ignite key by concatenating data. This is a standard distributed system pattern for key-value, and would allow the reader and writer consistently access the cache. The data is a combination of strings and integers. To simplify our use case, lets say its an email address

Re: How to do address resolution?

Hello! I can see the following in the thread dump: "main" #1 prio=5 os_prio=0 tid=0x7f02c400d800 nid=0x1e43 runnable [0x7f02cad1e000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.Net.poll(Native Method) at sun.nio.ch.SocketChannelImpl.poll(SocketChannelImpl.java:951) - locked

Re: Ignite Configuration file modify

Hello! You can implement this yourself if you really need it. Such as, you can watch an XML file, when it changes, do Ignition.loadSpringBin(file, bean name), and then call ignite.getOrCreateCache() on all cache configurations found in that bean. Regards. -- Ilya Kasnacheev вт, 30 июн. 2020

Re: Ignite Configuration file modify

Ok, well modifying the configuration might not be a good solution, what if you have multiple nodes and the configurations files no longer match, I guess you could create a service that runs on all nodes and have that updating the XML configuration files when you add caches, there is no need to

Re: Ignite Configuration file modify

Hello :) Because If I add cache by code, the cache disappears when the node is restarted so I want to modify the configuration file directly. Thank you! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Configuration file modify

Hi! No, you need to restart Ignite if you change xml configuration as far as I know. But you can add caches after Ignite is started without any problems, both from code and from SQL, is there any reason you cannot use one of these methods ? Den 2020-06-30 kl. 10:47, skrev kay: Hello, Is

Ignite Configuration file modify

Hello, Is there a way to modify the configuration file after Ignite Node starts? Should I use FTP directly to create a page to modify configuration file? I know I can add cache in ignite run time but after restart, There is not exist cache add in runtime. So I need to find a way modify