Re: Setting Cache Size using Max Records

Hi Denis, For our product we are using an in-house solution where we expose the size in records. Now we are looking at replacing it with Ignite. So we wanted to make the experience seamless and let the end user's continue to set the same configuration they are familiar with, rather than adding a

Re: Setting Cache Size using Max Records

Hi Vic, That’s unsupported for the off-heap memory. You can only limit memory usage based on the size in bytes. Please share more details of why this type of records eviction is needed. We might suggest an alternate solution. Denis On Wednesday, June 24, 2020, Victor wrote: > Hi, > > I am

Re: What does all partition owners have left the grid on the client side mean?

No, it's not. It's not clear when it happened and what was with the cluster and the client node itself at this moment. Evgenii ср, 24 июн. 2020 г. в 18:16, John Smith : > Ok I'll try... The stack trace isn't enough? > > On Wed., Jun. 24, 2020, 4:30 p.m. Evgenii Zhuravlev, < >

Re: What does all partition owners have left the grid on the client side mean?

Ok I'll try... The stack trace isn't enough? On Wed., Jun. 24, 2020, 4:30 p.m. Evgenii Zhuravlev, < e.zhuravlev...@gmail.com> wrote: > John, right, didn't notice them before. Can you share the full log for the > client node with an issue? > > Evgenii > > ср, 24 июн. 2020 г. в 12:29, John Smith :

Setting Cache Size using Max Records

Hi, I am looking to set the cache size for off-heap via number of max records instead of max bytes. Similar to how LRU eviction policy for on-heap can set it. Haven't found anything around that. Is that doable, if yes, how do i go about it? Thanks, Vic -- Sent from:

Re: What does all partition owners have left the grid on the client side mean?

John, right, didn't notice them before. Can you share the full log for the client node with an issue? Evgenii ср, 24 июн. 2020 г. в 12:29, John Smith : > I thought I did! The link doesn't have them? > > On Wed., Jun. 24, 2020, 2:43 p.m. Evgenii Zhuravlev, < > e.zhuravlev...@gmail.com> wrote: >

Re: What does all partition owners have left the grid on the client side mean?

I thought I did! The link doesn't have them? On Wed., Jun. 24, 2020, 2:43 p.m. Evgenii Zhuravlev, < e.zhuravlev...@gmail.com> wrote: > Can you share full log files from server nodes? > > ср, 24 июн. 2020 г. в 10:47, John Smith : > >> The logs for server are here: >>

Re: Ignite SSL security

Hi, Internally, Ignite will use new File(keyStoreFilePath) ... This will interpret the keyStoreFilePath relative to the process working directory. Use: System.out.println("Working Directory = " + System.getProperty("user.dir")); to determine your working dir. Then use:

Re: What does all partition owners have left the grid on the client side mean?

Can you share full log files from server nodes? ср, 24 июн. 2020 г. в 10:47, John Smith : > The logs for server are here: > https://www.dropbox.com/sh/ejcddp2gcml8qz2/AAD_VfUecE0hSNZX7wGbfDh3a?dl=0 > > The error from the client: > > javax.cache.CacheException: class >

Ignite SSL security

Hi Guru, I am try to implement the SSL security, default-config.xml like below, I have generated the server.jks and trust.jks with command 'keytool -genkey -alias ignite -keystore server.jks -keyalg RSA' and put the file server.jks to the $IGNITE_HOME folder, but when restart ignite, met below

Re: What does all partition owners have left the grid on the client side mean?

The logs for server are here: https://www.dropbox.com/sh/ejcddp2gcml8qz2/AAD_VfUecE0hSNZX7wGbfDh3a?dl=0 The error from the client: javax.cache.CacheException: class org.apache.ignite.internal.processors.cache.CacheInvalidStateException: Failed to execute cache operation (all partition owners

Re: What does all partition owners have left the grid on the client side mean?

Not sure about the wrong configuration... All the apps work this seems to happen every few weeks. We don't have any particular heavy load. I just bounced the client application and the errors went away. On Wed, 24 Jun 2020 at 12:57, Evgenii Zhuravlev wrote: > Hi, > > It means that there are no

Re: What does all partition owners have left the grid on the client side mean?

Hi, It means that there are no nodes in the cluster that holds certain partitions. So, probably you have a wrong configuration or some of the nodes left the cluster and you don't have backups in the cluster for these partitions. I believe more can be found from logs. Evgenii ср, 24 июн. 2020 г.

Re: What does all partition owners have left the grid on the client side mean?

Also I'm assuming that the thin client wouldn't be susceptible to this error? On Wed, 24 Jun 2020 at 12:38, John Smith wrote: > The cluster is showing active when running control.sh > > But the client is showing "all partition owners have left the grid" > > The client node is marked as

What does all partition owners have left the grid on the client side mean?

The cluster is showing active when running control.sh But the client is showing "all partition owners have left the grid" The client node is marked as client=true so it's not a server node. Is this split brain as well?

Re: GridIoManager compile error(2.8.0)

This should be a problem of your toolchain. If there were compilations issues we would not release those versions. The first thing to check is that you use JDK 8 to build the binary. The produced binary can work on other versions of JDK 9+. - Denis On Sun, Jun 21, 2020 at 6:21 PM 38797715

Re: Amazon AMI not available in a specific region

Ignite dev community, Could you remind me if we still updating the AWS images for our releases? If yes, how about expanding a list of supported regions? - Denis On Wed, Jun 24, 2020 at 6:10 AM Gandhi, Karthik wrote: > Hi - AWS Apache images are limited to 2 regions (US East 1 and US West >

Re: Thread starvations

Sorry the above log file doesn't contain all info. Please check this file Logs.zip -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Thread starvations

Thanks for the reply. We've done query analysis and found that pretty much all queries are taking around 1-5ms execution time for our operations which we consider it to be fine. But we have one query which is adding of rows in a table. We get maximum 5000 records at a time and we use

Amazon AMI not available in a specific region

Hi - AWS Apache images are limited to 2 regions (US East 1 and US West 1). I have a need to Install and configure ignite in US East 2 AWS region. Appreciate if can copy to this region -Karthik