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

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

GitHub user akalash opened a pull request:

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

    IGNITE-6552 ability to set WAL history size in MBytes

    

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

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

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

    https://github.com/apache/ignite/pull/3559.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 #3559
    
----
commit 10a7221392d00caa25f99f7f1aa33408c085e759
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-02-22T11:57:38Z

    IGNITE-6552 ability to set WAL history size in MBytes

commit 1bf01c091e064bc48fe49a3b750e1c47e68fbc4a
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-02-22T13:00:59Z

    IGNITE-6552 change FileDescriptor header

----


> The ability to set WAL history size in time units
> -------------------------------------------------
>
>                 Key: IGNITE-6552
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6552
>             Project: Ignite
>          Issue Type: Improvement
>          Components: persistence
>    Affects Versions: 2.2
>            Reporter: Vladislav Pyatkov
>            Assignee: Anton Kalashnikov
>            Priority: Major
>             Fix For: 2.5
>
>
> We can to set size of WAL history in number of checkpoints.
> {code}
> org.apache.ignite.configuration.PersistentStoreConfiguration#setWalHistorySize
> {code}
> But it is not convenient fro end user. Nobody to say how many checkpoint to 
> occur over several minutes.
> I think, it will be better if we will have ability to set WAL history size in 
> time units (milliseconds for example).



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

Reply via email to