[
https://issues.apache.org/jira/browse/IGNITE-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov resolved IGNITE-6940.
---------------------------------------
Resolution: Won't Fix
For now Ignite already dump threads to log when starvation is detected.
Timeout for tasks and jobs can be set using IgniteCompute.withTimeout method.
Task monitoring will be implemented as system view (new ticket will be created).
> Thread Starvation monitoring
> ----------------------------
>
> Key: IGNITE-6940
> URL: https://issues.apache.org/jira/browse/IGNITE-6940
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Kuznetsov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: iep-7
> Fix For: 2.5
>
>
> Ignite Thread Pools Starvation
> Description
> This situation can occur if user submits tasks that recursively submit more
> tasks and synchronously wait for results. Jobs arrive to worker nodes and are
> queued forever since there are no free threads in public pool since all
> threads are waiting for job results.
> Detection and Solution
> Task timeout can be set for tasks, so task gets canceled automatically.
> Web Console should provide ability to cancel any task and job from UI.
> Report
> Timed out tasks and jobs should be reported on Web Console and reported to
> logs. We need to introduce new config property to set timeout for reported
> jobs.
> Log record and Web Console should include:
> - Master node ID
> - Start time
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
