Re: Possible dead lock when number of jobs exceeds thread pool

Hi Raymond, Yes. Bringing C# client in sync with Java version is on plans. Of course, C# client will always be a bit outdated in terms of features of Java client. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Possible dead lock when number of jobs exceeds thread pool

Hi Alex, Thanks for clarifying. I have been testing increasing the public pool size and it does help. Is there a general work programme to bring the C# client into parity with the Java client? Thanks, Raymond. Sent from my iPhone > On 6/10/2017, at 2:26 AM, afedotov wrote: > > Hi Raymo

RE: Possible dead lock when number of jobs exceeds thread pool

Hi Raymond, You are right. As for now, C# API doesn't support WithExecutor calls. Please find a corresponding ticket for your reference https://issues.apache.org/jira/browse/IGNITE-6566 In this case. You could increase the public thread pool

RE: Possible dead lock when number of jobs exceeds thread pool

...@trimble.com] Sent: Thursday, October 5, 2017 10:52 AM To: 'user@ignite.apache.org' Subject: RE: Possible dead lock when number of jobs exceeds thread pool It seems that the C# API does not support custom thread pools. There is no WithExecutor() method on ICompute, and looking at the clien

RE: Possible dead lock when number of jobs exceeds thread pool

ymond Wilson [mailto:raymond_wil...@trimble.com] Sent: Thursday, October 5, 2017 9:23 AM To: 'user@ignite.apache.org' Subject: RE: Possible dead lock when number of jobs exceeds thread pool Alex, Thanks for the pointer to the custom thread pools. The ExecutorConfiguration aspect of the gri

RE: Possible dead lock when number of jobs exceeds thread pool

[mailto:alexander.fedot...@gmail.com] Sent: Thursday, October 5, 2017 4:07 AM To: user@ignite.apache.org Subject: RE: Possible dead lock when number of jobs exceeds thread pool Raymond, Yes. Your understanding is correct, that should be the reason of starvation. Please take a look at custom thread pools https

RE: Possible dead lock when number of jobs exceeds thread pool

Raymond, Yes. Your understanding is correct, that should be the reason of starvation. Please take a look at custom thread pools https://apacheignite.readme.io/v2.2/docs/thread-pools#section-custom-thread-pools. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Possible dead lock when number of jobs exceeds thread pool

e- From: afedotov [mailto:alexander.fedot...@gmail.com] Sent: Wednesday, October 4, 2017 10:37 PM To: user@ignite.apache.org Subject: Re: Possible dead lock when number of jobs exceeds thread pool Hi, That actually looks like a starvation in public pool where compute tasks are processed. Please

Re: Possible dead lock when number of jobs exceeds thread pool

Hi, That actually looks like a starvation in public pool where compute tasks are processed. Please share PerformRenderer() source. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Possible dead lock when number of jobs exceeds thread pool

I am testing an aspect of a POC I have written in C# to determine how well it performs when processing multiple tasks at one time. I’m using Ignite 2.2. Briefly, a client node sends a request to a server node for a list of items. Each of the items requested is send back to a listener in the clie