You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/12/09 12:48:02 UTC
[jira] [Updated] (IGNITE-4393) Need to remove code putting cache
operations to sequence
[ https://issues.apache.org/jira/browse/IGNITE-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-4393:
------------------------------------
Fix Version/s: (was: 1.9)
2.0
> Need to remove code putting cache operations to sequence
> --------------------------------------------------------
>
> Key: IGNITE-4393
> URL: https://issues.apache.org/jira/browse/IGNITE-4393
> Project: Ignite
> Issue Type: Improvement
> Reporter: Yakov Zhdanov
> Assignee: Semen Boikov
> Fix For: 2.0
>
>
> Currently Ignite guarantees that async operations started from the same thread are applied in the same order. This code will be literally useless once we move to thread per partition model.
> org.apache.ignite.internal.processors.cache.GridCacheAdapter#toggleAsync
> org.apache.ignite.internal.processors.cache.GridCacheAdapter#asyncOpAcquire
> org.apache.ignite.internal.processors.cache.GridCacheAdapter#asyncOpRelease
> org.apache.ignite.internal.processors.cache.GridCacheAdapter#asyncOpsSem
> org.apache.ignite.internal.processors.cache.GridCacheAdapter#lastFut
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.FutureHolder
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)