Eduard,
I tried the following to reproduce segfaults according to your description:
* Start Ignite server node
* Infinite loop, perform Cache.Put operations
* In the same loop access Process.HandleCount property
On Ubuntu 16.04, .NET Core 2.2.103 I see no crashes.
Can you please provide more deta
Hi Denis,
We already know that using the thin client introduces an extra network hop,
and to minimice its impact we've deployed a thick client node colocated
with our application and every application instance connects to the local
Ignite node.
We'd love to continue using the Ignite.NET thick cli
Please continue using Ignite.NET thick client until we release
partition-awareness for the thin one. That feature has been already
developed and to be released in Ignite 2.8.
Presently, the thin client sends all the request via the proxy which is one
of the server nodes it's connected to. While th
@ignite.apache.org
Subject: .NET thin client multithreaded?
Hello everyone,
We have just developed a gRPC service in .NET core that performs a bunch of
cache gets for every RPC. We've been using the Apache.NET nuGet starting the
Ignite node in client mode (thick client) but we just changed it to use the
Hello everyone,
We have just developed a gRPC service in .NET core that performs a bunch of
cache gets for every RPC. We've been using the Apache.NET nuGet starting
the Ignite node in client mode (thick client) but we just changed it to use
the thin client and we see much much worse response times
