[
https://issues.apache.org/jira/browse/IGNITE-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2820:
------------------------------------
Fix Version/s: (was: 1.7)
1.6
> IGFS: Ensure that all participating IDs are locked right after TX start.
> ------------------------------------------------------------------------
>
> Key: IGNITE-2820
> URL: https://issues.apache.org/jira/browse/IGNITE-2820
> Project: Ignite
> Issue Type: Task
> Components: IGFS
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Critical
> Fix For: 1.6
>
>
> *Problem*
> Sometimes we have to create new entries during some operation on metadata. If
> we do not lock this ID along with other participating IDs right after TX
> start, subsequent cache operation on this ID will result in network calls to
> block this key on other nodes.
> *Solution*
> Create potentially new key before entering TX and lock it with other keys.
> This should decrease number of network calls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
