You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yaroslav Molochkov (Jira)" <ji...@apache.org> on 2020/11/03 15:08:00 UTC
[jira] [Updated] (IGNITE-13575) Invalid blocking section in
GridNioWorker and GridNioClientWorker leads to false positive blocking
thread detection
[ https://issues.apache.org/jira/browse/IGNITE-13575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yaroslav Molochkov updated IGNITE-13575:
----------------------------------------
Fix Version/s: 2.9.1
> 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)