.... I have tried using the Async variants of the, but this does not change the number of public threads required in the Ignite server that is the recipient of the call (which I guess is sensible when I think about it).
-----Original Message----- From: Raymond Wilson [mailto:raymond_wil...@trimble.com] Sent: Thursday, October 5, 2017 10:52 AM To: 'user@ignite.apache.org' <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 client source I don't see any relevant executor support. Is this due to the Async method variants supported on the C# API? -----Original Message----- From: Raymond Wilson [mailto:raymond_wil...@trimble.com] Sent: Thursday, October 5, 2017 9:23 AM To: 'user@ignite.apache.org' <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 grid configuration does not appear to be present in the C# API. Is this only supported in the XML configuration file for C# clients? Raymond. -----Original Message----- From: afedotov [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://apacheignite.readme.io/v2.2/docs/thread-pools#section-custom-threa d-pools. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
