RE: Ignite nodes crash after firing heavy SQL query

Hi Craig, Yes, query is returning many records. But, we can not control who executes which type of command. However, cluster should be stable enough to handle such queries. Somewhere I have seen below few properties for the same, are those not available in Ignite open source? 1.

Re: Can ignite kv put data, sql query data in C/S mode?

full config file, and test code will be put here. server-config2.xml IgniteClients.java -- Sent from:

Can ignite kv put data, sql query data in C/S mode?

with ignite 2.10.0 C/S deploy mode, I'm trying to mix using K/V and sql query in a certain cache. Ignite server config like this(cacheconfiguration-queryEntities attribute):

Namespace and DsicoverSpi Properties for Ignite running on Kubernetes

I have two questions regarding how to set up Ignite in Kubernetes. Do all nodes need to be in the same namespace? E.G. If I have a thick client and a server node, do both need to be in the same name space to form a cluster? >From my research I think the answer is yes they need to be in the same

[Ignite Summit] The most popular question after Ignite Summit

Hi Igniters! 24 speakers, 15 hours, attendees from 49 countries, and 100+ people listening to each talk - the Summit was a great event for the community! Many thanks to our great speakers, resourceful hosts, smart experts who answered questions at the booth, and of course to everyone who attended,

Re: BinaryInvalidTypeException: Requesting mapping from grid failed for error reading cache

Joan, If persistence is not used then remove/move your work dir completely and restart. Check that your classpath doesn't contain duplicate classes for the same type. These might be in separate jars w/the same package and name, but be different inside. Take a look at

RE: Ignite nodes crash after firing heavy SQL query

Can you provide the query and the explain plan of the query (via Ignite Web Console)? First step I would suggest is to seek to tune the query, maybe it needs an index, or the driving table needs to be changed, or maybe the query uses indexes correctly but many rows are returned from the

Re: Ignite throws "Failed to resolve class name" Exception

Hi Ilya, Sorry I get back to you late. I have key-value classes on the server node. The peer class loading is enabled. I'm not getting this error consistently so it's hard to reproduce. Below is the code snippet that throws the error: First I got CacheState object with tableName as the key:

Re: Sorting result of ScanQuery

A scan isn’t ordered. As you suspect, the way to order queries in Ignite is to use SQL. You don’t need to use annotations to define your SQL fields, indexes, etc. A slightly more verbose way is to use Query Entities (indexes

Sorting result of ScanQuery

Hello everyone, I'm new to the community and fairly new to Apache Ignite. I have a question for which I couldn't find a confirmation if it's possible or not. I have a use case where I need to persist a certain POJO to an ignite cluster. The POJO can not be changed, so adding @SqlQueryField to

Ignite nodes crash after firing heavy SQL query

Hi Igniters, We want to use Ignite (v2.7.6) mostly via SQL for operational activities (adding extra indexes to enable querying). While doing POC, observed that if any heavy query is fired, few nodes from the clusters are going down due to 'OOM Error'. 1. Is there any way available to kill

Re: Failed to parse query. Column "...._KEY" not found;SQL statement:

"_key" and "_val" are predefined column names returning full key and value objects: select _key, _val from CommonConstruction On Wed, May 26, 2021 at 12:52 PM JP wrote: > Hi, > Thanks for reply.Appriciated. > Please use SqlFieldsQuery and list specific columns. > Actually i m getting

Re: Failed to parse query. Column "...._KEY" not found;SQL statement:

Hi, Thanks for reply.Appriciated. Please use SqlFieldsQuery and list specific columns. Actually i m getting values corresponding to the query column. how to get key value pair as result instead of getting list of value using SqlFieldsQuery .Any sample query reference if possible. Thanks in

Re: Failed to parse query. Column "...._KEY" not found;SQL statement:

Now I see the problem - you use SqlQuery, which is deprecated (obsolete) and has some limitations. Please use SqlFieldsQuery and list specific columns. Alternatively, use Ignite LINQ provider [1] to perform strongly-typed SQL queries, for example: CommonConstruction.AsCacheQueryable()

Re: Failed to parse query. Column "...._KEY" not found;SQL statement:

1. What if you do "select * from CommonConstruction" - does it work? yes it is working with sqlquery. 2. Can you try listing specific columns instead of "*"? if i am using specific column then i have to go with sqlfieldsquery instead of using sqlquery. -- Sent from:

Re: Ignite node heap gradually increasing and not getting stabilized

Not a direct answer, but there were a lot of improvements to thin clients in Ignite 2.10, specifically in cases where there are many connections. > On 26 May 2021, at 09:44, Naveen wrote: > > Just reopening this issue. > Unfortunately I could not analyze the heap dump which is of 25GB, so I

Re: Ignite node heap gradually increasing and not getting stabilized

Just reopening this issue. Unfortunately I could not analyze the heap dump which is of 25GB, so I could not do any analysis with this. What else can go wrong, however I could see 500 to 800 active thin client connections on each node, can this cause this I see our heap memory utilization is

Re: 2.8.1 : INFO org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted incoming communication connection

Hi all, Continuation of this post ( Page 1 : http://apache-ignite-users.70518.x6.nabble.com/2-8-1-INFO-org-apache-ignite-spi-communication-tcp-TcpCommunicationSpi-Accepted-incoming-communicatin-td33854.html Page 2 :

Re: Thin client access Ignite cluster with ZooKeeper Discovery

Hi! I'm afraid that it is impossible. If you are using ZookeperDiscovery (not TcpDiscovery with TcpDiscoveryZookeeperIpFinder, this is important!), every ignite node maintains EPHEMERAL_SEQUENTIAL znode in /apacheIgnite/n/. But it doesn't contains any information regarding ip addresses, node

Re: Failed to parse query. Column "...._KEY" not found;SQL statement:

1. What if you do "select * from CommonConstruction" - does it work? 2. Can you try listing specific columns instead of "*"? On Wed, May 26, 2021 at 6:24 AM JP wrote: > Hi, > I am with Apache Ignite V2.9.1.And using .net thin client to perform query > on cache. > And using cache query as

Re: IN Operator not working with sub query on different cache

Hi, IN operator has some limitations in Ignite, it is recommended to use joins instead [1] As I understand from your second message, with JOIN you get correct results. [1] https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-performance-and-usability-considerations On Tue, May