[
https://issues.apache.org/jira/browse/IGNITE-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Konstantinov updated IGNITE-9993:
----------------------------------------
Summary: Some values cached in WB store are locked during a batch flush
(was: Values cached in WB store are locked during a batch flush)
> Some values cached in WB store are locked during a batch flush
> --------------------------------------------------------------
>
> Key: IGNITE-9993
> URL: https://issues.apache.org/jira/browse/IGNITE-9993
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.6
> Reporter: Dmitry Konstantinov
> Priority: Major
>
> The following logic is executed under write lock within flushing logic:
> {code:java}
> applyBatch(pending, true, null);
> {code}
> [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L1120]
> In combination with IGNITE-5003 it may cause locking of a put/remove
> operation for the first value in next batch while the whole current batch is
> applying.
> applyBatch(pending, true, null); should be moved out of the lock guarded
> section.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
