Exception using ThinClient in dotnet core

. [cid:0b597528-59f1-48a9-890d-41533e1ee55e] Regards, Stéphane Gayet Responsable Développement / Development Manager [https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/55370421467418375936059118036679301217_5e30230b86cfde000a68f219_8e82e6302fdca8989b5eec24209877fa.png] (+33) 1 70 38

RE: Ignite on GCP / GKE

Thanks, Maxim. I will give it a try :) Stéphane Gayet Responsable Développement / Development Manager [https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/55370421467418375936059118036679301217_5b8eb5cb514093000719db66_8e82e6302fdca8989b5eec24209877fa.png] (+33) 1 70 38 70 74 +33 6 00 00

Ignite on GCP / GKE

Hi All, Does someone have any experience about hosting Ignite on Google GCP / GKE ? I read the documentation on Kubernetes deployment on google cloud, but if someone can share its experience on: * performances * persistance, * cost, * ... Thanks Stéphane Gayet Responsable

RE: Apache.Ignite.EntityFramework

Hi Pavel, Thanks for your reply. Any date ? Regards Stéphane Gayet Responsable Développement / Development Manager [https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/55370421467418375936059118036679301217.png] (+33) 1 70 38 70 74 [https://storage.letsignit.com

Apache.Ignite.EntityFramework

Hi, Apache.Ignite.EntityFramework is built using EntityFramework 6.2.0. Do you plan to release a version using EntityFrameworkCore? Regards Stéphane Gayet Responsable Développement / Development Manager [https://storage.letsignit.com/5b884a1a1e0a0f0007c51472

RE: Affinity colocation and sql queries

Thanks Ilya, Denis. Regards, De : ilya.kasnacheev Envoyé : mardi 5 juin 2018 18:15:45 À : user@ignite.apache.org Objet : Re: Affinity colocation and sql queries Hello! 1) Yes! 2) "almost all the time" is not a very strong constraint here. You might need to en

Affinity colocation and sql queries

part of the sql query? If yes, should it be indexed? 4/ Or, this doesn't work but it will if I split each subset in different caches and define affinity key as above. cache1 = subset items with key "key1" cache2 = subset items with key "key2" ... 5/ Or, nope, there is no way to achieve that. Regards, Stéphane Gayet

RE: SQL Query error

Hi Ilya, Ok, I will update if error raises again. Thanks and regards De : ilya.kasnacheev Envoyé : vendredi 1 juin 2018 18:52:48 À : user@ignite.apache.org Objet : RE: SQL Query error Hello! Unfortunately, from those stack traces it looks like nothing is hap

RE: SQL Query error

k) from all nodes on the nearest occassion when you notice that cluster is stuck again. Regards, -- Ilya Kasnacheev 2018-05-31 14:01 GMT+03:00 Stéphane Gayet mailto:stephane.ga...@misterfly.com>>: Hi Ilya, Thanks for your help. Could you access to the files at https://drive.goo

RE: SQL Query error

: SQL Query error Hello! Full Ignite logs of the problematic node will be helpful. Can you upload the log file anywhere? Regards, -- Ilya Kasnacheev 2018-05-31 12:37 GMT+03:00 Stéphane Gayet mailto:stephane.ga...@misterfly.com>>: Hi All, Corrections about my previous email. When the c

RE: SQL Query error

his node, the cluster starts responding again. So my questions are : why the node stops responding? How to identify root causes? Regards, Stephane Gayet ____ De : Stéphane Gayet Envoyé : mercredi 30 mai 2018 23:44 À : user@ignite.apache.org Objet : SQL Query error

SQL Query error

Hi all, We have installed a 2.4 Ignite cluster - 3 nodes under Windows systems (24 Go, 16 Go, 16 Go) - 4 caches configured, partitioned, no backup - no persistence cache @c0 contains around 60,000 items, cache @c3 contains few items (around 200) but items are very large. We run sql querie