ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1778) IGFS: Implement rollback procedure: cleanup the "reserved" data.
Date Thu, 17 Mar 2016 11:44:33 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov updated IGNITE-1778:
------------------------------------
    Summary: IGFS: Implement rollback procedure: cleanup the "reserved" data.  (was: IGFS:
implement rollback procedure: cleanup the "reserved" data.)

> IGFS: Implement rollback procedure: cleanup the "reserved" data.
> ----------------------------------------------------------------
>
>                 Key: IGNITE-1778
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1778
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Ivan Veselovsky
>            Assignee: Vladimir Ozerov
>             Fix For: 1.6
>
>
> 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)

Mime
View raw message