[
https://issues.apache.org/jira/browse/IGNITE-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-15012:
-------------------------------------
Description:
It is necessary to adapt the historical rebalance to the release of WAL
segments after their reservation. Since IGNITE-14952 will be automatically
released when the maximum is reached.
This following proposal is part (in bold) of a discussion at [dev
list|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]:
{code:java}
Main proposal:
When theDataStorageConfiguration#getMaxWalArchiveSize is reached, cancel and do
not give the reservation of the WAL segments until we reach
DataStorageConfiguration#getWalArchiveSize. In this case,* if there is no
segment for historical rebalance, we will automatically switch to full
rebalance.*
{code}
was:
It is necessary to adapt the historical rebalance to the release of WAL
segments after their reservation. Since IGNITE-14952 will be automatically
released when the maximum is reached.
This following proposal is part (in bold) of a discussion at [dev
list|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]:
{noformat}
Main proposal:
When theDataStorageConfiguration#getMaxWalArchiveSize is reached, cancel and do
not give the reservation of the WAL segments until we reach
DataStorageConfiguration#getWalArchiveSize. In this case,* if there is no
segment for historical rebalance, we will automatically switch to full
rebalance.*
{noformat}
> Adapting historical rebalance to segment release
> ------------------------------------------------
>
> Key: IGNITE-15012
> URL: https://issues.apache.org/jira/browse/IGNITE-15012
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Fix For: 2.12
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It is necessary to adapt the historical rebalance to the release of WAL
> segments after their reservation. Since IGNITE-14952 will be automatically
> released when the maximum is reached.
> This following proposal is part (in bold) of a discussion at [dev
> list|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]:
> {code:java}
> Main proposal:
> When theDataStorageConfiguration#getMaxWalArchiveSize is reached, cancel and
> do not give the reservation of the WAL segments until we reach
> DataStorageConfiguration#getWalArchiveSize. In this case,* if there is no
> segment for historical rebalance, we will automatically switch to full
> rebalance.*
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
