You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Atri Sharma (Jira)" <ji...@apache.org> on 2021/07/01 07:52:00 UTC
[jira] [Assigned] (IGNITE-15043) FifoQueueCollisionSPI Should Be
Thread Safe
[ https://issues.apache.org/jira/browse/IGNITE-15043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Atri Sharma reassigned IGNITE-15043:
------------------------------------
Assignee: Atri Sharma
> FifoQueueCollisionSPI Should Be Thread Safe
> -------------------------------------------
>
> Key: IGNITE-15043
> URL: https://issues.apache.org/jira/browse/IGNITE-15043
> Project: Ignite
> Issue Type: Bug
> Reporter: Atri Sharma
> Assignee: Atri Sharma
> Priority: Major
>
> Today, if there is a single slot available in the active jobs limit and N tasks come concurrently, there is a chance that many (or all) of them will be able to proceed because the logic of FifoQueueCollisionSPI is as follows:
> 1. Get active tasks count
> 2. Compare to max tasks count
> 3. If less, start the task
> This is not thread safe, and we need to provide a realistic view of active tasks count to all threads.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)