Hello!
It's impossible to answer this question without going into specifics of
your use case, which I don't have. Maybe you have a case to show?
Regards,
--
Ilya Kasnacheev
пт, 23 авг. 2019 г. в 16:22, narges saleh :
> Hello Ilya
>
> There are parallel streams inserting data for all the count
Hi Stan,
Yes, the second app I referred to is using Java thing client. My Ignite version
is 2.7.5, for all apps in question.
The cache key type is one of our domain objects which has just three String
variables; I don’t think there’s anything unusual about it. I’m not explicitly
setting any Bi
Hello,
Most probably the reason is different default values of compactFooter
property of BinaryConfiguration for thin client and server (false for
client, true for server).
Here is a ticket: [1]
You can work around this by setting BinaryConfiguration including this
property explicitly.
[1] : http
Hello!
This looks like a mistake. However, we're going to drop IGFS so the fix is
unlikely to be expected.
The recommended practical approach is to increase number of threads in
system thread pool to large value.
Regards,
--
Ilya Kasnacheev
вт, 27 авг. 2019 г. в 00:34, Chris Software :
> Hel
I see. Thank you.
On Tue, Aug 27, 2019 at 12:30 PM Ilya Kasnacheev
wrote:
> Hello!
>
> This looks like a mistake. However, we're going to drop IGFS so the fix is
> unlikely to be expected.
>
> The recommended practical approach is to increase number of threads in
> system thread pool to large v
Hi, running 2.7.0
I noticed one of my nodes was down. It seems to have turned itself off,
because of: Ignite node is in invalid state due to a critical failure.
I attached logs here:
https://www.dropbox.com/s/82li1020a5ig4ty/ignite-failled.log?dl=0
Hi guys -I have a three node cluster in which one node has 192GB ram and 48
cores and (i call this manager as it does some heavy lifting) and other 2
nodes have 60GB ram and 36 cores. ( worker nodes). I am getting following
exception ramdomly :
[2019-08-28 03:03:52,346][ERROR][client-connector-#
