Re: Threadpools and .WithExecute() for C# clients

The source of inbound requests into Server A is from client applications. Server B is really a cluster of servers that are performing clustered transformations and computations across a data set. I originally used IComputeJob and similar functions which work very well but have the restriction tha

Re: CacheEntryProcessor causes cluster node to stop

Hi Vladimir, here is logs from other node ignite-3.zip - İbrahim Halil Altun Senior Software Engineer @ Segmentify -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Random CorruptedTreeException from Apache Ignite

Hi Maxim, we are facing the exact same problem :( Is it ok/safe to remove cacheGroupName from the code that is already been created on nodes? If so, when we start our applications from the updated code will we be still have access to same caches or new caches will be created on nodes? - İb

Re: CacheEntryProcessor causes cluster node to stop

Hi, It seems that the root cause of the issue happens on node with id=fb70df1c-0311-48b4-bb33-88cdf85438ce. That node becomes unresponsive. Could you please share logs from that node, it could help? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Threadpools and .WithExecute() for C# clients

Hi, Can you share a more detailed use case, please? Right now it’s not clear why do you need a messaging fabric. If you are interesting in a progress tracking, then you could try a CacheAPI or QueryContinious, for example. What are the sources of inbound requests? Is it a client requests? Wha

Re: Metrics for Ignite

Hello, I would suggest to refer to following metrics and use MX bean: https://apacheignite.readme.io/docs/cache-metrics, there are average metrics for get/put/remove. I'm not entirely sure if you really do want to have some internal benchmarking for each operation, how big are workloads going to

CacheEntryProcessor causes cluster node to stop

Hi Igniters, Although class was deployed in SHARED or CONTINUOUS mode node got exception and halted itself. log added; ignite.zip *Ignite version*: 2.7.5 *Cluster size*: 16 *Client size*: 22 *Cluster OS version*: Centos

Log4j2 problem

Hi! I have setup the log4j2 logger and everything works fine until I shutdown the application (2.7.5), I run it with ignite.bat and I have my own code in a LifeCycleBean, I have some code in beforeNodeStop() and some code in afterNodeStop() and it looks like the log4j2 logger stops working be

NegativeArraySizeException on cluster rebalance

Hi Igniters, We are getting negativearraysizeexception on one of our cacheGroups rebalancing period. I am adding the details that I could get from logs; *Ignite version*: 2.7.5 *Cluster size*: 16 *Client size*: 22 *Cluster OS version*: Centos 7 *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x

Re: Threadpools and .WithExecute() for C# clients

Hi Alexandr, To summarise from the original thread, say I have server A that accepts requests. It contacts server B in order to help processing those requests. Server B sends in-progress results to server A using the Ignite messaging fabric. If the thread pool in server A is saturated with inbound

RE: Threadpools and .WithExecute() for C# clients

Hi, Raymond! As far as I can see, there are no plans for porting custom executors configuration in .NET client right now [1]. Please, remind, why do you need a separate pool instead of a default PublicPool? [1] - https://issues.apache.org/jira/browse/IGNITE-6566 From: Raymond Wilson Sent: We

Re: Declaring server side CacheEntryListenerin Ignte config

Hi, Could you please provide more details about your case? Generally, for tracking of the cache updates in Ignite you can use Events: https://apacheignite.readme.io/docs/events Continuous Queries: https://apacheignite.readme.io/docs/continuous-queries CacheInterceptor: https://ignite.apache

Threadpools and .WithExecute() for C# clients

Some time ago I ran into and issue with thread pool exhaustion and deadlocking in AI 2.2. This is the original thread: http://apache-ignite-users.70518.x6.nabble.com/Possible-dead-lock-when-number-of-jobs-exceeds-thread-pool-td17262.html At the time .WithExecutor() was not implemented in the C#