.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 thin client and we see much much worse response times

Re: Node failure with "Failed to write buffer." error

Ivan, Alex Goncharuk, The exception trace is not helpful, it's not obvious what might be a reason and how to address it. How do we tackle these problems? Ibrahim, please attach all the log files for a detailed look. - Denis On Thu, Aug 22, 2019 at 3:08 AM ihalilaltun wrote: > Hi folks, > > W

Re: Capacity planning for production deployment on kubernetes

Please share the whole log file. It might be the case that something goes wrong with volumes you attached to Ignite pods. - Denis On Thu, Aug 22, 2019 at 8:07 AM Shiva Kumar wrote: > Hi Denis, > > Thanks for your response, > yes in our test also we have seen OOM errors and pod crash. > so we w

Re: Using Ignite as blob store?

How about setting page size to more KBs or MBs based on the average value? That should work perfectly fine. - Denis On Thu, Aug 22, 2019 at 8:11 AM Shane Duan wrote: > Thanks, Ilya. The blob size varies from a few KBs to a few MBs. > > Cheers, > Shane > > > On Thu, Aug 22, 2019 at 5:02 AM Ilya

Re: questions

I am not sure you can find real world examples where caches can be evenly partitioned, if the partitioning factor is an affinity key. I comparing, with partitioning case with relational databases, say partitioning based on month of the year. I definitely don't have 100s of departments but I do have

Re: questions

Hello! 1) No. Ignite only rebalances data when nodes are joining or leaving cluster. 2) Ignite's affinity is not really well suited to such detailed manual assignment. It is assumed that your cache has large number of partitions (e.g. 1024) and data is distributed evenly between all partitions. Ha

Re: questions

Thanks Ilya for replies. 1) Doesn't ignite rebalance the nodes if there are additional nodes available and the data doesn't fit the cache current ignite node? Consider a scenario where I have 100 pods on a physical node, assuming pod = ignite node. 2) I am not sure what you mean by confining half

Re: Using Ignite as blob store?

Thanks, Ilya. The blob size varies from a few KBs to a few MBs. Cheers, Shane On Thu, Aug 22, 2019 at 5:02 AM Ilya Kasnacheev wrote: > Hello! > > How large are these blobs? Ignite is going to divide blobs into <4k > chunks. We have no special optimizations for storing large key-value pairs. >

Re: Capacity planning for production deployment on kubernetes

Hi Denis, Thanks for your response, yes in our test also we have seen OOM errors and pod crash. so we will follow the recommendation for RAM requirements and also I was checking to ignite documentation on disk space required for WAL + WAL archive. here in this link https://apacheignite.readme.io/d

Re: Capacity planning for production deployment on kubernetes

Shivakumar, Such allocation doesn’t allow full memory utilization, so it’s possible, that nodes will crash because of out of memory errors. So, it’s better to follow the given recommendation. If you want us to investigate reasons of the failures, please provide logs and configuration of the fai

Re: Memory usage metric doesn't come down when memory is freed up

Hello! When you get IgniteOOM, your node is now in incorrect state where behavior is undefined. You should plan carefully to avoid getting IOOM on nodes, or enable persistence/page eviction. Regards, On 2019/08/15 13:16:26, colinc wrote: > I am using the Ignite metrics API to monitor memory

Re: One of Ignite pod keeps crashing and not joining the cluster

Hi, Please share - Ignite version you're running - Exact steps and events (a node was restarted, a client joined, etc) - Logs of all three servers Thanks, Stan On Mon, Aug 19, 2019 at 3:27 PM radha jai wrote: > Hi , > Ignite being deployed on the kubernetes, there were 3 replicas of ignite >

Re: Using Ignite as blob store?

Hello! How large are these blobs? Ignite is going to divide blobs into <4k chunks. We have no special optimizations for storing large key-value pairs. Regards, -- Ilya Kasnacheev чт, 22 авг. 2019 г. в 02:53, Shane Duan : > Hi Igniters, is it a good idea to use Ignite(with persistence) as a bl

Re: questions

Hello! 1) When there is an overflow, either page eviction kicks in, or, if it is disabled, you get an IgniteOOM, after which the node is no longer usable. Please avoid overflowing any data regions since there's no graceful handling currently. 2) I don't think so. You can't easily confine half of c

Re: Does IgniteCache.containsKey lock the key in a Transaction?

Yohan, IgniteCache#containsKey(...) locks a key under pessimistic transactions with REPEATABLE_READ isolation level, just like a get(). And it doesn’t make servers send values back to a request

Re: Cache spreading to new nodes

Marco, IgniteCache.localEntries .iterator() will iterate over all entries in the cache on a local node. So, it doesn't iterate over caches, but over entries

Node failure with "Failed to write buffer." error

Hi folks, We have been experiencing node failures with the error "Failed to write buffer." recently. Any ideas or optimizations not to get the error and node failure? Thanks... [2019-08-22T01:20:55,916][ERROR][wal-write-worker%null-#221][] Critical system error detected. Will be handled accordin

Re: Ignite backup/restore Cache-wise

GridGain Snapshots allow you to take a backup on a live, working cluster. If you can allow to stop the cluster activity while snapshot is being taken you can: - Deactive the cluster (e.g. control.sh --deactivate) - Copy the persistence files (you would need work/binary_meta, work/marshaller, work/d

Question on submitted post

Hi there, How long does it usually take, for a post to be seen on the forum? Maybe I made a mistake so I will provide my question here. Excuse me if I am being impatient: = Good afternoon everyone, I have recently run into an issue and I think the problem