ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6720) Move operation with file system outside checkpoint write lock
Date Thu, 26 Oct 2017 13:05:01 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220401#comment-16220401

Alexey Goncharuk commented on IGNITE-6720:


1) Use Ignite future instead of j.u.c.Future, this is a project-wide convention
2) Use U.error instead of log.error()

Otherwise, looks good.

> 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

View raw message