Is there some tools to get Node `ConsistentID`?

Hi, Guys: Is there some tools to get `ConsistentID` of the server node? I found the `ID` in topology is not `ConsistentID` -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How much heap to allocate

Hi, I am getting the following warning when starting Ignite - " Nodes started on local machine require more than 20% of physical RAM what can lead to significant slowdown due to swapping " The 20% is a typo in version 2.5, it should be 80%. We have increased the max size of the default region t

Re: Slow SQL query uses only a single CPU

Thanks, I tried the composite key and provided the index tip in the query but the query plan and execution time stayed the same. So really I am back to where we started. Right now I suspect that I am not setting the affinity key properly - I intend the key to be customer_id, but maybe Ignite sets

Re: Affinity key in SQL execution

Ok, I tried to write generic impl to use the same key class with different caches . That's why kept the name affinityId. The reason I am not getting error is I have the subscriptionId in Data(value) class as well. So it means the affinity key field name matters. I was thinking/trying to map the af

Re: Separate Storage Device for Ignite cluster nodes Persistence Data

Hi, If it's possible to work with a shared storage using Java file APIs then you can use it for Ignite persistence. -- Denis On Wed, Aug 22, 2018 at 10:37 AM siva wrote: > Hi, > > Is it possible to store persistence data of each cluster node in Azure > storage device(blob,datalake etc.) inste

Re: has the following been resolved since 2.3? (jdbc thin client security)

Vladimir, This ticket [1] can be closed, right? All the thing clients in Ignite 2.6 go with authentication capabilities. However, not sure what's the status of the other task [2]. [1] https://issues.apache.org/jira/browse/IGNITE-6941 [2] https://issues.apache.org/jira/browse/IGNITE-6856 On Wed,

Re: Affinity key in SQL execution

Prasad, In this case using subscriptionId in query would be a syntax error, because the name of the field is affinityId. If you use affinityId, however, Ignite will route the query to a single node. It knows that it's affinity key based on @AffinityKeyMapped annotation. -Val -- Sent from: http

Re: Slow SQL query uses only a single CPU

1. /* PUBLIC.AFFINITY_KEY */ means index on affinity column is used. Full index will be scanned against date condition. As I wrote you can create composite index to speedup index scan. 2. "group sorted" means index is used for grouping. Looks like H2 have optimization for this and grouping can appl

Separate Storage Device for Ignite cluster nodes Persistence Data

Hi, Is it possible to store persistence data of each cluster node in Azure storage device(blob,datalake etc.) instead of storing in each node's disc. Ex: Assume 3 server nodes on 3 different machines(probably on Azure Cloud VM's) with Ignite Native persistence enabled.So data will be store in

Re: Slow SQL query uses only a single CPU

Just as a reference, bellow are 2 execution plans with and without the index on a very similar table. Adding the index remove /* PUBLIC.AFFINITY_KEY */ and /* group sorted */. 1) Does PUBLIC.AFFINITY_KEY mean that DT is the affinity key. We are setting customer_id as an affinity key. Is there a wa

Re: Runtime failure on bounds

Hi, Sorry, I missed this conversation. To understand your problem you should provide the reproducer, cache configuration or steps how we can reproduce it or file the issue with all this information. At the moment it's not cleared how to solve it. BR, Andrei -- Sent from: http://apache-ignite-

Re: Apache Ignite SQL- read Only User Creation

Hi, Yes, when you are using ignite advance security (not GridSecurityProcessor interface) then you are able only to manage the password. https://apacheignite.readme.io/docs/advanced-security provides the simple password authentification security. You can only: 1)Create the user - https://apachei

Re: Slow SQL query uses only a single CPU

Thanks Andrey, We are using the Ignite notebook, any idea if there is a way to provide these flags and hints directly from SQL? >From your description, it seems like the query is executed in the following order 1) Group by customer_id 2) For each group, perform the filtering on date using the ind

Re: Slow SQL query uses only a single CPU

Eugene, 1. Note that queryParallelism splits indices and Ignite work similar way as if index data resides on several nodes. These index part can be looked up in parallel threads. 2. It is not a simple query as you data distributed among partitions and is not collocated and aggregate function are u

Re: Slow SQL query uses only a single CPU

Thanks Andrey, Right now we are testing with only one big node, so the reduce step should not take any time. 1) We already set parallelism to 32, and I can still see only 1 core working. Anything else could be preventing multiple cores from working on the job? 2) Why would the reduce phase need t

Re: In the case of read-through cache, both Replicated and Partitioned mode are identical?

Hi, CacheStore semantic suppose you will warm-up a cache via calling cache.loadCache(). When you use read-through and forget load cache from back store then it is ok if no backups are updated on read operation. Backups and replicated cache in case of read-through just add some tolerance to node-l

Re: In the case of read-through cache, both Replicated and Partitioned mode are identical?

I am just wondering would you really need backup partitions in case of replicated mode? The whole data is replicated, so I think each node itself is kind of backup for other. On Wed, Aug 22, 2018, 2:41 PM yonggu.lee wrote: > I have a read-through cache backed by a hbase table. I this case, is

Re: Can't write to Ignite cluster when one node in baseline is down

Hi, It's ok for the case when you run without backups, because you lose partitions here. Do you start a new cache each time or reuse the cache from the different run? When you use persistence, Ignite persists cache's metadata on disk and if you change cache configuration after that, these changes

Unix timestamp conversion problem

Now the time stamp of conversion positive number is not a problem, but the time of conversion negative number is not accurate, is this BUG, which god has encountered again -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: case sensitive Apache ignite.net SQL query

Hi, The workaround is to use UPPER SQL function: var _arg = new object[] { "%ABC%" }; new SqlQuery(typeof(CustomerModel), "UPPER(CustomerName) like ?", _arg) Pavel On Wed, Aug 22, 2018 at 12:15 PM Evgenii Zhuravlev wrote: > Hi, > > As for now, Ignite SQL is case-sensitive. There are plans to

Re: case sensitive Apache ignite.net SQL query

Hi, As for now, Ignite SQL is case-sensitive. There are plans to support case-insensitive search in SQL in future, here is the ticket: https://issues.apache.org/jira/browse/IGNITE-3999 Evgenii ср, 22 авг. 2018 г. в 12:04, shuvendu < shuvendu@travelcentrictechnology.com>: > Hi, > > How to ma

In the case of read-through cache, both Replicated and Partitioned mode are identical?

I have a read-through cache backed by a hbase table. I this case, is there no difference between Replicated and Partitioned mode? When I tested, although I set up a Replicated mode, the cache only had Primary, and not Backup part (in web console, monitoring tab) -- Sent from: http://apache-i

case sensitive Apache ignite.net SQL query

Hi, How to make apache ignite sqlquery to ignore case. for example var _arg = new object[] { "%abc%" }; new SqlQuery(typeof(CustomerModel), "CustomerName like ?", _arg) var _arg = new object[] { "%ABC%" }; new SqlQuery(typeof(CustomerModel), "CustomerName like ?", _arg) i am getting differen

has the following been resolved since 2.3? (jdbc thin client security)

https://issues.apache.org/jira/browse/IGNITE-6856 https://issues.apache.org/jira/browse/IGNITE-6941 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Slow SQL query uses only a single CPU

Hi, 1. Possible there are too much data should be looked for the query. With single node and parallelism=1 query will always run in single thread. You can try to add more nodes or increase query parallelism to utilize more CPU cores. 2. Index on date field may be not effective as reduce phase sh