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
Hello!
Unfortunately, from those stack traces it looks like nothing is happening on
the cluster at the moment.
Can you wait for "Failed to wait for partition map exchange" message to
start appearing in logs, and then collect stack traces?
Regards,
--
Sent from:
om/drive/folders/1apPraUn-Z2wKXFr5Wsdf8qHIQssW0XgC?usp=sharing
Regards,
De : Ilya Kasnacheev
mailto:ilya.kasnach...@gmail.com>>
Envoyé : jeudi 31 mai 2018 12:32:35
À : user@ignite.apache.org<mailto:user@ignite.apache.org>
Objet : Re: SQL Query error
Hello!
ssW0XgC?usp=sharing
>
>
> Regards,
> --
> *De :* Ilya Kasnacheev
> *Envoyé :* jeudi 31 mai 2018 12:32:35
> *À :* user@ignite.apache.org
> *Objet :* Re: SQL Query error
>
> Hello!
>
> Full Ignite logs of the problematic node will be helpful. Can you
: 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
A.Ignite\MrFly.CacheDlm.Common\Services\ServiceCache.cs:ligne
> 646
>
>
> If I stop Ignite on this node, the cluster starts responding again.
>
>
> So my questions are : why the node stops responding? How to identify root
> causes?
>
>
> Regards,
>
> Stephane Gayet
>
ode, 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
Hi
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