Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Sample import org.apache.ignite.Ignite; import org.apache.ignite.Ignition; import org.apache.ignite.configuration.*; import org.apache.ignite.events.EventType; import org.apache.ignite.failure.StopNodeOrHaltFailureHandler; import org.apache.ignite.internal.util.IgniteUtils; import

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

public class SampleTest { static String localhost; private static Random random; final static int discPort = 36101; final static int commPort = 37601; final static int sharedMemPort = 37235; final static int clusterSize = 2; private static final int messageQueueLimit

Re: Fastest way to iterate over a persistence cache

Hi, of course we are using SSDs, but 4kB is still a tiny amount, when you have to wait for the SSD read roundtrip every time. The CPU is idle at about 10%.. The Linux kernel does not seem to perform a readahead, probably because of the random access structure. For some reason the

help with control.sh script

I'm testing a 32 nodes cluster with a partitioned cache with one backup. If 2 of them crashed (not if, when) I have the lost partitions problem. Now I ssh to one of the nodes and execute *control.sh --baseline.* >From every node other than the one marked as "coordinator" (?) I get this output:

Is there any way to get cache and node status programatically?

Is there any API or recommended way to get if a node is Online or Offline programmatically the same way control script does? Also, once a cache is moved to read-only state, I can't find a way to get that status? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Fastest way to iterate over a persistence cache

You may need to do the parallelism “manually.” Something like: for (int p = 0; p < ignite.affinity("TEST").partitions(); p++) { ignite.compute().affinityRunAsync(Arrays.asList("TEST"), p, () -> { ScanQuery q = new ScanQuery() .setPartition(p);

List all available distributed locks in cluster

Hi all, Is there a way to list all available distributed locks within the cluster? Would be nice to allow some sort of monitoring about used locks and their correct disposal by our application. In fact I'm looking for something similar to: org.apache.ignite.Ignite#cacheNames but for locks.

Re: Abrupt stop of application on using sql

Hi Ilya, How is decreasing maxSize of data region related to "Buffer Overflow" problem? I mean we dont get any Out of memory log in DeMsg logs and also "top" command shows enough available RAM. We tried decreasing maxSize to 50mb now but the problem still persists. Can this also be related to

Re: Is Geo redundancy supported in Ignite

Hello! The one I know of, yes. Regards, -- Ilya Kasnacheev чт, 15 апр. 2021 г. в 09:30, Venkata Bhagavatula : > Hi Ilya Kasnacheev, > > We are also looking for this. > Can you please highlight the third party solution? I know that GridGain > supports this in their entrerprise solution. Is

Re: Ignite unable to understand recursive query.

Hello! As far as my understanding goes, Ignite does not support recursive CTE. You may still try running it as a local query by setting local=true in your connection/query settings. Regards, -- Ilya Kasnacheev чт, 15 апр. 2021 г. в 02:33, PunxsutawneyPhil3 : > I am having a problem with the

Re: Is Geo redundancy supported in Ignite

Hi Ilya Kasnacheev, We are also looking for this. Can you please highlight the third party solution? I know that GridGain supports this in their entrerprise solution. Is this you are referring to ? Thanks n Regards, Chalapathi On Tue, Apr 13, 2021 at 6:29 PM Ilya Kasnacheev wrote: > Hello!