[jira] [Created] (IGNITE-12892) Clarify WAL archive size configuration

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (IGNITE-12892) Clarify WAL archive size configuration

Anton Vinogradov (Jira)
Semyon Danilov created IGNITE-12892:
---------------------------------------

             Summary: 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


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)