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 requests, then there are no available threads to service the messaging fabric traffic from server B to server A resulting in a deadlock condition.
In the original discussion it was suggested creating a custom thread pool to handle the Server B to Server A traffic would resolve it. Thanks, Raymond. On Wed, Jul 17, 2019 at 9:48 PM Alexandr Shapkin <[email protected]> wrote: > 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 <[email protected]> > *Sent: *Wednesday, July 17, 2019 10:58 AM > *To: *user <[email protected]> > *Subject: *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# client so there > was little option but to expand the size of the public thread pool > sufficiently to prevent the deadlocking. > > > > We have been revisiting this issue and see that .WithExecutor() is not > supported in the AI 2.7.5 client. > > > > Can this be supported in the C# client, or is there a workaround in the > .Net environment? that does not require this capability? > > > > Thanks, > > Raymond. > > > > >
