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/08/03 09:59:21 UTC
[jira] [Updated] (IGNITE-1778) IGFS: Implement rollback procedure:
cleanup the "reserved" data.
[ https://issues.apache.org/jira/browse/IGNITE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-1778:
------------------------------------
Fix Version/s: (was: 1.7)
1.8
> IGFS: Implement rollback procedure: cleanup the "reserved" data.
> ----------------------------------------------------------------
>
> Key: IGNITE-1778
> URL: https://issues.apache.org/jira/browse/IGNITE-1778
> Project: Ignite
> Issue Type: Task
> Components: IGFS
> Affects Versions: 1.6
> Reporter: Ivan Veselovsky
> Fix For: 1.8
>
>
> The following procedure is applied if the file is locked:
> 1) take Node id from the lock Id.
> 2) see via discovery service if this node is alive.
> 3) if yes, return (we cannot lock the file).
> 4) if not: do a rollback:
> - delete all the blocks in "reserved" range from the data cache.
> - set reserved range to zero.
> - remove the lock from the FileInfo.
> The above procedure should be performed upon every attempt to take a lock, and (may be) periodically while traversing the file system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)