[
https://issues.apache.org/jira/browse/IGNITE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415847#comment-16415847
]
ASF GitHub Bot commented on IGNITE-8017:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3707
IGNITE-8017
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8017
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3707.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 #3707
----
----
> Disable WAL during initial preloading
> -------------------------------------
>
> Key: IGNITE-8017
> URL: https://issues.apache.org/jira/browse/IGNITE-8017
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ilya Lantukh
> Assignee: Ilya Lantukh
> Priority: Major
>
> While handling SupplyMessage, node handles each supplied data entry
> separately, which causes a WAL record for each entry to be written. It
> significantly limits preloading speed.
> We can improve rebalancing speed and reduce pressure on disk by disabling WAL
> until all data is loaded. The disadvantage of this approach is that data
> might get corrupted if node crashes - but node that crashed during preloading
> has to clear all it's data anyway. However, it is important to distinguish
> situations when new node joined cluster or added to baseline topology (and
> doesn't hold any data) and when additional partitions got assigned to node
> after baseline topology changed (in this case node has to keep all data in
> consistent state).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
