[jira] [Commented] (IGNITE-13575) Invalid blocking section in GridNioWorker and GridNioClientWorker leads to false positive blocking thread detection

["Vyacheslav Koptilin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-13575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236081#comment-17236081 ] 

Vyacheslav Koptilin commented on IGNITE-13575:
----------------------------------------------

Hello [~ivandasch],

Could you please take a look at this comment https://github.com/apache/ignite/commit/88b5f4798a4a2ff3f5c1e7c981b7927a8a06854b#r44376175 ?

> Invalid blocking section in GridNioWorker and GridNioClientWorker leads to false positive blocking thread detection
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13575
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13575
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.9, 2.8.1
>            Reporter: Ivan Daschinskiy
>            Assignee: Ivan Daschinskiy
>            Priority: Major
>              Labels: 2.9.1-rc
>             Fix For: 2.10, 2.9.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If {{IGNITE_SYSTEM_WORKER_BLOCKED_TIMEOUT}} less than 2000 ms, then simple {{epoll_wait}} for 2000 on idle cluster is considered as critical failure. 
> We should surround {{selector.select}} with {{blockingSectionBegin}} and {{blockingSectionEnd}} instead of {{updateHeartbeat}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)