[
https://issues.apache.org/jira/browse/IGNITE-12892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246344#comment-17246344
]
Ignite TC Bot commented on IGNITE-12892:
----------------------------------------
{panel:title=Branch: [pull/8550/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8550/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5778904&buildTypeId=IgniteTests24Java8_RunAll]
> Clarify WAL archive size configuration
> --------------------------------------
>
> Key: IGNITE-12892
> URL: https://issues.apache.org/jira/browse/IGNITE-12892
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Actual maximum size of WAL archive that can be reserved for historical
> rebalance is calculated as minimum of three properties:
> # DataStorageConfiguration#walHistSize (units: number of checkpoints)
> # DataStorageConfiguration#maxWalArchiveSize (units: bytes)
> # IgniteSystemProperties#IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE
> (units: number of checkpoints)
> The logic is a little unclear, so I propose following changes:
> # Stop using walHistSize at all (it's already deprecated) for WAL truncation
> # Use IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE only in case WAL archive
> is managed externally (so we limit the quantity of checkpoints stored in
> memory, but don't remove WAL files)
> # Use -1 for maxWalArchiveSize (instead of Long.MAX_VALUE) to disable WAL
> truncation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
