[
https://issues.apache.org/jira/browse/IGNITE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713073#comment-14713073
]
ASF GitHub Bot commented on IGNITE-1299:
----------------------------------------
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/39
IGNITE-1299: retry file meta unlock transactions introduced.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite ignite-1299
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/39.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #39
----
commit 542fae14e653f8c67146162038f884fbe902ed4b
Author: iveselovskiy <iveselovs...@gridgain.com>
Date: 2015-08-26T13:00:28Z
IGNITE-1299: retry file meta unlock transactions introduced.
----
> IGFS: file meta unlock transaction should be retried on failure.
> ----------------------------------------------------------------
>
> Key: IGNITE-1299
> URL: https://issues.apache.org/jira/browse/IGNITE-1299
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: ignite-1.4
> Reporter: Ivan Veselovsky
> Assignee: Ivan Veselovsky
> Fix For: ignite-1.4
>
>
> Tests written to check behavior IGNITE-1277 revealed problems on file data
> writing when some nodes have left the topology (see tests added in
> IGNITE-1277).
> In particular, it seems that upon a node stop the transaction unlocking the
> file meta can be failed , and by the current design will never be retried.
> To fix that we seem to need to add an unlock transaction retries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
