Re: defaultDataRegionConfiguration is per-node or per-cluster?

Hi, maxSize and initialSize are per-node values. In your example, if you have more then one node with this configuration, each node will allocate 16GB off-heap memory. чт, 23 авг. 2018 г. в 18:04, yfernando : > Hi All, > > When setting the defaultDataRegionConfiguration parameter in the >

Re: Is there some tools to get Node `ConsistentID`?

It will be available in Visor CMD in Ignite 2.7 See https://issues.apache.org/jira/browse/IGNITE-8506 (with screenshot). On Thu, Aug 23, 2018 at 4:23 PM Ilya Kasnacheev wrote: > Hello! > > How about ignite.cluster().localNode().consistentId()? > > Regards, > > -- > Ilya Kasnacheev > >

Re: Affinity key in SQL execution

Problem is resolved now. The index type setting in cache configuration was incorrect. After setting DefaultDataAffinityKey.class in cache config index type query executed successfully. New sql is as follows. I have few questions on it. 1) Execution plan is showing 2 sqls. What does second sql

defaultDataRegionConfiguration is per-node or per-cluster?

Hi All, When setting the defaultDataRegionConfiguration parameter in the IgniteConfiguration, are the maxSize and initialSize values per-node or cluster-wide? Ex: specifying 16GB for the Default_Region. Is the 16GB reserved on the node or reserved across the entire cluster?

Re: Affinity key in SQL execution

Hi, Problem is resolved now. The index type setting in cache configuration was incorrect. After setting DefaultDataAffinityKey.class in cache config index type query executed successfully. New sql is as follows. I have couple of questions on it. 1) Execution plan is showing 2 sqls. What does

Re: Stupide question about Queue ?

Have IgniteQueues been made persistent in subsequent releases of ignite ? If not, there are there any plans for the same in forthcoming releases ? thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

CTE and Recursive CTE support in SQL

When Common Table Expression (CTE) and Recursive CTE are planned to be part of supported SQL syntax ? It would be super productive to have Support for CTE as we can do Graph like Traversals and many complex queries. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: CTE and Recursive CTE support in SQL

Hello! Apache Ignite already has CTE support (but not Recursive CTE). I think that we have inherited it from H2. Regards, -- Ilya Kasnacheev 2018-08-23 15:34 GMT+03:00 piyush : > When Common Table Expression (CTE) and Recursive CTE are planned to be part > of supported SQL syntax ? > > It

Re: Ignite default partition to node mapping is not balanced

Hello! It is a pseudo-random function based on consistentId. Maybe you have consistentId specified for your nodes (or for some reason they are the same anyway). Theoretically you could heuristically pick consistentIds for nodes for better distribution. I don't think you can work around

Re: Ignite default partition to node mapping is not balanced

Hi We are not running with ignite persistence. Also we observed that for a given ignite nodes the partition to node mapping is always same using RendezvousAffinityFunction or not or how many times we restart the cluster. How can we say its random ? I would like to know what is the solution to

Re: Is there some tools to get Node `ConsistentID`?

Hello! How about ignite.cluster().localNode().consistentId()? Regards, -- Ilya Kasnacheev 2018-08-23 4:17 GMT+03:00 huzx : > Hi, Guys: > > Is there some tools to get `ConsistentID` of the server node? I found > the `ID` in topology is not `ConsistentID` > > > > -- > Sent from:

Re: Ignite default partition to node mapping is not balanced

Hello! If you would read on the Rendezvous algorithm you will notice that it is essentially random-based. Balanced distribution is only attained by having a large number of partitions, which would even-out the randomness. Also, if all of your partitions map to the same nodes, you should check

Ignite default partition to node mapping is not balanced

Hi I'm working on an Ignite project where all the data is partitioned based on field partition-id and it is set as affinitykeyfield. We are running 5 ignite servers on 5 machines which have identical hardware and ignite heap settings/java options. Our data has overall 5 partition-ids(1-5) . But

Re: Affinity key in SQL execution

Hi, I tried your suggestion but I am getting query parsing error now. I am attaching my data and data key class in this mail. Could you please help me out? SQL : select assetGroupId, name from AssetGroupData where affinityId = ? *Exception:* javax.cache.CacheException: Failed to parse query.