Insert with JDBC Thin driver into caches

Hi, I have the following scenario: 1. I create a cache using the java API with a CacheConfiguration with a QueryEntity and some fields on it. 2. I put some data into that cache using SQL INSERT statements with the JDBC Thin driver 3. I read this data using the java API with IgniteCache.get(Key) I

Re: [2.10 branch]cpp thin client transaction :Transaction with id 1 not found.

Hello! Can you prepare a simple reproducer? I can start two server nodes and launch it specifying their addresses as parameters. If there needs to be any specific node configuration, please share also. Regards, -- Ilya Kasnacheev пн, 15 февр. 2021 г. в 15:08, jjimeno : > Hello > > No, both b

Re: Ignite Startup Warnings

Sorry for my late answer, I did not get the notification about new postings in this thread Disabling checkpoint SPI logging and collision SPI logging was pretty easy: Config: // ### Disable checkpoint spi using nop implementation config.setCheckpointSpi(new NopCheckpointSpi()); /

Re: Ignite 2.9.1 - An existing connection was forcibly closed by the remote host

Hello, Thanks for your help, As per our network team, there were no packet drops between client and server. Do I need to collect either jvm thread dump or IIS worker process thread dump ? Thanks & Regards, Charlin On Mon, 15 Feb 2021 at 16:40, Ilya Kasnacheev wrote: > Hello! > > I think I've

Re: [2.10 branch]cpp thin client transaction :Transaction with id 1 not found.

Hello No, both belong to the same cluster. Waiting for the PutAll fix, we want to benchmark multi-node reading performance. For that we: - create a single server node cluster - create a single cache with 1.8M keys and ~1GB in it - create a single c++ thin node with a single endpoint (the host co

Re: [2.10 branch]cpp thin client transaction :Transaction with id 1 not found.

Hello! Is it possible that two endpoints do not represent two nodes of the same cluster, but rather form two separate single-node clusters? In that case you may expect such errors, I guess. Especially if you reliably break down one cluster with your 1GB transaction and then it tries to rollover t

Re: Reliably duplicate SQL cache

Hello! Two tables have different name of an indexed binary type by default. Try repo.query("create table page1(a varchar, b varchar, c varchar, PRIMARY KEY (a, b)) WITH \"cache_name=page1, key_type=PageKey, value_type=Page\"") repo.query("create table page2(a varchar, b varchar, c varchar, PRIMAR

Re: [2.9.1] Out of memory in data region

Hello, That's what I was thinking of... thanks Ilya -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.9.1 - An existing connection was forcibly closed by the remote host

Hello! I think I've just answered the same question for 2.8.1: https://lists.apache.org/thread.html/r102cf85775f7759e6772ceeed6d3a6843ea736b20647020fb8374833%40%3Cuser.ignite.apache.org%3E I'm not sure why your node does not recognize itself as SEGMENTED. [15:04:29,711][SEVERE][tcp-client-disco-s

Re: [2.9.1] Out of memory in data region

Hello! I think it's quite possible to run out of off-heap if your transactions are comparable with your data region in time. Ignite needs to do page eviction to be able to reuse off-heap pages, but I guess that pages relevant to currently running transactions can't be evicted. Regards, -- Ilya K

Re: SQL queries on the Ignite cache fail, cannot find table

Hello! Have you tried SELECT * FROM "PersonCache".PERSON? Regards, -- Ilya Kasnacheev вс, 14 февр. 2021 г. в 01:33, PunxsutawneyPhil3 : > I am trying to configure Ignite to act as a cache with a Postgres database. > > I have started with the example on the Ignite website, using an xml > confi

Re: [MEETUP] Apache Ignite at Dutch Railways. Join the talk on February 16

See you tomorrow! Join us 8 AM Pacific Standard Time / 5 PM Central European Time чт, 4 февр. 2021 г. в 17:23, Kseniya Romanova : > Hi Igniters! > > Here’s the cool case of Ignite in production. Every day, millions of > people travel by train through the Netherlands—on one of the busiest rail > i

Re: System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

Hello Thanks for your help. I will try with the tryget option. Thanks & Regards, Charlin On Mon, 15 Feb 2021 at 13:39, Pavel Tupitsyn wrote: > Hi Charlin, > > Most likely you should use a single *TryGet *[1] call instead of > ContainsKey + Get, > it achieves the same logic more efficiently

Re: System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

Hi Charlin, Most likely you should use a single *TryGet *[1] call instead of ContainsKey + Get, it achieves the same logic more efficiently and without the risk of race conditions. Looks like the key gets removed in between the ContainsKey and Get calls by another thread / process / node. [1] ht