[
https://issues.apache.org/jira/browse/IGNITE-16470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-16470:
-------------------------------------
Description:
Currently, {{walForceArchiveTimeout}} switch to the new WAL segment even if not
DataEntry was logged.
We can perform a switch only if DataEntry was logged so there are new data for
CDC.
was:
It seems that we may always use
{{walForceArchiveTimeout}} instead of {{walAutoArchiveAfterInactivity}},
because only guarantee user needs is "WAL records available in archive after
timeout".
This statement should be discussed on the dev-list to be sure we fully
understand all use-cases for {{walAutoArchiveAfterInactivity}}
> Rollout on walForceArchiveTimeout only if DataEntry loged
> ---------------------------------------------------------
>
> Key: IGNITE-16470
> URL: https://issues.apache.org/jira/browse/IGNITE-16470
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: IEP-59
>
> Currently, {{walForceArchiveTimeout}} switch to the new WAL segment even if
> not DataEntry was logged.
> We can perform a switch only if DataEntry was logged so there are new data
> for CDC.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
