Re: Adding SQL Support to an Existing Cache

Hello! - No. - Yes. - Yes. Regards, -- Ilya Kasnacheev ср, 5 июн. 2019 г. в 19:20, anicn : > I'm curious to hear more about what considerations there are. For example: > - Is any of the cache data duplicated in the table? > - Are there indexes created for the primary key on this table? > - Do

Re: unable to query the cache after restart

Hello! Does the query work before the restart? Regards, -- Ilya Kasnacheev ср, 5 июн. 2019 г. в 22:37, goutham manchikatla : > Hi, > > I have an Ignite SQL cache setup with persistence enabled and loaded the > cache with 10 million records. > Once I do a cache restart, I get an empty response

Re: Is there any way to force recover the cluster - copying running cluster datastore

I would discourage you from doing this if data consistency is prominent for you. What you see on the disk of one cluster node might be inconsistent with the whole cluster state and the actual/last updates in memory. Snapshots and backups can solve your task. Google for a solution provided by GridGa

Re: how does group by works in ignite

Hi David, Please check this thread to see if you need to stay with Postgres or switch to Ignite: https://stackoverflow.com/questions/55208376/apache-ignite-vs-sql-server-performance/55230967#55230967 In general, it's expected that Ignite is to be used for relational DBs acceleration - when those

Re: unable to query the cache after restart

Yes , the query worked before restart. On Thu, Jun 6, 2019 at 4:16 AM Ilya Kasnacheev wrote: > Hello! > > Does the query work before the restart? > > Regards, > > -- > Ilya Kasnacheev > > > ср, 5 июн. 2019 г. в 22:37, goutham manchikatla : > >> Hi, >> >> I have an Ignite SQL cache setup with per

RE: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore

Thanks for the update Denis. If one of the WAL disk gets failed, is there any way to start or recover the cluster forcefully ? Thanks and Regards, Kamlesh Joshi From: Denis Magda Sent: Thursday, June 6, 2019 4:44 PM To: user@ignite.apache.org Subject: [External]Re: Is there any way to force re

Re: unable to query the cache after restart

Hello! This is strange. What's cache configuration? Is there a reproducer? Did you change the code between restarts, including key/value types, if any? Regards, -- Ilya Kasnacheev чт, 6 июн. 2019 г. в 16:16, goutham manchikatla : > Yes , the query worked before restart. > > On Thu, Jun 6, 201

Re: unable to query the cache after restart

Hi, I didn't change any code between restarts. Below is the configuration.

Re: unable to query the cache after restart

Hello! Looks OK. Can you reproduce the behavior, or is it a one-time occurrence? What happens if you try to scan that cache? Anything suspicious in your logs? Regards, -- Ilya Kasnacheev чт, 6 июн. 2019 г. в 18:30, goutham manchikatla : > Hi, > > I didn't change any code between restarts. Bel

Re: unable to query the cache after restart

Hi, I reproduced the behavior. I stopped the cache nodes and started them again. I see the metadata, cache count, but no query response: {"successStatus":0,"sessionToken":"94DAD112C4E848E98663AF5883BBDDE2","response":[{"cacheName":"lincs_cache","types":["Account"],"keyClasses":{"Account":"java.la

Re: unable to query the cache after restart

Hello! What's the query in question? Have you tried using e.g. sqlline to connect via JDBC? Regards, -- Ilya Kasnacheev чт, 6 июн. 2019 г. в 19:15, goutham manchikatla : > Hi, > > I reproduced the behavior. I stopped the cache nodes and started them > again. I see the metadata, cache count, b

Re: unable to query the cache after restart

http://localhost:8080/ignite?user=ignite&password=ignite&cmd=qryexe&type=Account&pageSize=10&cacheName=lincs_cache&qry=select%20*%20from%20lincs.account%20LIMIT%2010 Yes I tried using Debeaver JDBC, query -*SELECT* * *FROM* LINCS.ACCOUNT *LIMIT* 10; Still the same behavior. On Thu, Jun 6, 2019 a

Re: unable to query the cache after restart

Hello! Can you make a reproducer project which will exhibit this behavior? One which will fill enough data in cache so that this behavior is observable after restart. BTW, what's the version you are on? Have you tried scan query (via Java code)? Regards, -- Ilya Kasnacheev чт, 6 июн. 2019 г.

Sudden cluster failure

Hi! Ignite version is 2.4 We have 2 server nodes and 4 client nodes. Suddenly on one client node we have repeating messages: 2019.05.31 11:19:57.066 INFO [grid-nio-worker-tcp-comm-2-#59%ITLXCLKICP-client6fdfcde3-3e30-406f-8272-cb61a8a4cc80%] TcpCommunicationSpi - Accepted incoming communication

Re: unable to query the cache after restart

Hi, I will work on the reproducer project. I am using 2.7 version. Also I tried with Java SQL API SqlFieldsQuery sql = *new* SqlFieldsQuery(query); QueryCursor> cursor = cache.query(sql) On Thu, Jun 6, 2019 at 10:32 AM Ilya Kasnacheev wrote: > Hello! > > Can you make a reproducer project whic