You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Veselovsky (JIRA)" <ji...@apache.org> on 2015/08/26 11:35:45 UTC
[jira] [Created] (IGNITE-1305) IGFS: file meta should be unlocked
even if the node is stopping
Ivan Veselovsky created IGNITE-1305:
---------------------------------------
Summary: IGFS: file meta should be unlocked even if the node is stopping
Key: IGNITE-1305
URL: https://issues.apache.org/jira/browse/IGNITE-1305
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky
Fix For: ignite-1.5
Method org.apache.ignite.internal.processors.igfs.IgfsMetaManager#unlock is currently implemented in such a way, that if we failed to take "busyLock", we throw "Node is stopping" exeption, and the file meta unlcoking does not happen (see code snippet below). In some cases this may lead to situation when due to node stop the file will stay locked forever.
{code}
if (busyLock.enterBusy()) {
try {
// unlock implementation goes there
}
finally {
busyLock.leaveBusy();
}
}
else
throw new IllegalStateException("Failed to unlock file system entry because Grid is stopping: " + info);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)