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

ASF GitHub Bot commented on IGNITE-8282:
----------------------------------------

GitHub user dspavlov opened a pull request:

    https://github.com/apache/ignite/pull/3832

    IGNITE-8282 Direct IO: support fdatasync, which does not flush modified 
metadata

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8282

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3832.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 #3832
    
----
commit f5fbd1a8951f73897aaadea2656ec35ede852762
Author: dpavlov <dpavlov@...>
Date:   2018-04-16T14:36:02Z

    IGNITE-7182 Supported striped dirty page storage in skip list maps and 
quick sort with early cp pages write start

commit a9d19313a711765f702610b2d56488f58735fa70
Author: dpavlov <dpavlov@...>
Date:   2018-04-16T14:46:56Z

    IGNITE-8282 Direct IO: support fdatasync, which does not flush modified 
metadata

----


> Direct IO: support fdatasync, which does not flush modified metadata
> --------------------------------------------------------------------
>
>                 Key: IGNITE-8282
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8282
>             Project: Ignite
>          Issue Type: Improvement
>          Components: persistence
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>            Priority: Major
>             Fix For: 2.6
>
>
> fsync(2) - Linux man page
> fdatasync() is similar to fsync(), but does not flush modified metadata 
> unless that metadata is needed in order to allow a subsequent data retrieval 
> to be correctly handled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to