Hi Alexey, Thanks for bringing this up.
> Does this look like a drastic and maybe a breaking change to anybody? It sounds like a breaking change to me as it can easily break existing use-cases after an upgrade if someone relies on the default values. Even if this is mentioned in the release notes, there's no guarantee that the person performing the upgrade knows about all the use-cases that rely on a long AHM (or that they read the release notes carefully before upgrading). Furthermore, if someone has backup/restore enabled and forgets changing the value while upgrading, an incremental backup cannot be retried after setting it, because the historical data is gone, so they have to do a full backup again. > If yes, what alternatives should we consider instead? I would simply suggest adding it into the known issues section on the website with the suggested workaround. Additionally, we could log a warning at startup linking to the known issues page if the setting if the value of --tablet_history_max_age_sec is higher than 15 minutes. - Attila
