[
https://issues.apache.org/jira/browse/IGNITE-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216663#comment-16216663
]
ASF GitHub Bot commented on IGNITE-6720:
----------------------------------------
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/2912
IGNITE-6720 Move operation with file system outside checkpoint write …
…lock
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6720
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2912.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 #2912
----
commit fd58fb9e76b2f4888df6fe058be5531cc4ed91f0
Author: Eduard Shangareev <[email protected]>
Date: 2017-10-24T09:48:39Z
IGNITE-6720 Move operation with file system outside checkpoint write lock
----
> Move operation with file system outside checkpoint write lock
> -------------------------------------------------------------
>
> Key: IGNITE-6720
> URL: https://issues.apache.org/jira/browse/IGNITE-6720
> Project: Ignite
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
> Reporter: Eduard Shangareev
> Assignee: Eduard Shangareev
>
> There could be long-running operation in onMarkCheckPointBegin call.
> So, to move them outside write lock holding block make possible make some
> operations possible to async (for example, making onMarkCheckPointBegin
> return Future).
> During this block is in progress no caches updated are allowed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
