[
https://issues.apache.org/jira/browse/HDDS-13268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-13268:
----------------------------------
Labels: pull-request-available (was: )
> [Docs] Advanced topics: troubleshooting OM snapshot installation
> ----------------------------------------------------------------
>
> Key: HDDS-13268
> URL: https://issues.apache.org/jira/browse/HDDS-13268
> Project: Apache Ozone
> Issue Type: Task
> Components: OM HA, Ozone Manager
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
> Labels: pull-request-available
>
> [https://github.com/apache/ozone/pull/8600#pullrequestreview-2925327285]
> Create a new user doc page for "Troubleshooting OM HA snapshot installation
> issues"
> {quote}I think it is worth adding how to handle an issue that we encountered
> before that because of the a huge OM DB, while the follower's install the
> snapshot from leader (i.e. download the OM DB), the leader's Raft log for the
> particular snapshot index has already been purged. So after the OM follower
> finished downloading the OM DB, the leader cannot send the purged logs and
> request to follower to redownload the OM DB.
> Currently, this can be handled by setting the configurations introduced in
> HDDS-8131. So either:
> # Set {{ozone.om.ratis.log.purge.preservation.log.num}} to a high enough
> value (e.g. 1000000) so that the OM leader will not the purge the last N logs.
> # Set {{ozone.om.ratis.log.purge.upto.snapshot.index}} to false, which
> causes OM leader logs to never be purged until all the follower already catch
> up.
> You can refer to the ticket for a full explanation and tradeoffs.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
