[
https://issues.apache.org/jira/browse/HDDS-1649?focusedWorklogId=279446&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-279446
]
ASF GitHub Bot logged work on HDDS-1649:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jul/19 03:02
Start Date: 19/Jul/19 03:02
Worklog Time Spent: 10m
Work Description: arp7 commented on pull request #948: HDDS-1649. On
installSnapshot notification from OM leader, download checkpoint and reload OM
state
URL: https://github.com/apache/hadoop/pull/948#discussion_r305186358
##########
File path:
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/OMConfigKeys.java
##########
@@ -123,6 +123,9 @@ private OMConfigKeys() {
"ozone.om.ratis.log.appender.queue.byte-limit";
public static final String
OZONE_OM_RATIS_LOG_APPENDER_QUEUE_BYTE_LIMIT_DEFAULT = "32MB";
+ public static final String OZONE_OM_RATIS_LOG_PURGE_GAP =
+ "ozone.om.ratis.log.purge.gap";
+ public static final int OZONE_OM_RATIS_LOG_PURGE_GAP_DEFAULT = 1000000;
Review comment:
Good suggestion! Let me file a followup jira to fix that. Want to get this
patch committed today, it's been hanging around for over a month.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 279446)
Time Spent: 11h 40m (was: 11.5h)
> On installSnapshot notification from OM leader, download checkpoint and
> reload OM state
> ---------------------------------------------------------------------------------------
>
> Key: HDDS-1649
> URL: https://issues.apache.org/jira/browse/HDDS-1649
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Labels: pull-request-available
> Time Spent: 11h 40m
> Remaining Estimate: 0h
>
> Installing a DB checkpoint on the OM involves following steps:
> 1. When an OM follower receives installSnapshot notification from OM leader,
> it should initiate a new checkpoint on the OM leader and download that
> checkpoint through Http.
> 2. After downloading the checkpoint, the StateMachine must be paused so that
> the old OM DB can be replaced with the new downloaded checkpoint.
> 3. The OM should be reloaded with the new state . All the services having a
> dependency on the OM DB (such as MetadataManager, KeyManager etc.) must be
> re-initialized/ restarted.
> 4. Once the OM is ready with the new state, the state machine must be
> unpaused to resume participating in the Ratis ring.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
