[
https://issues.apache.org/jira/browse/HDDS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656033#comment-16656033
]
Jitendra Nath Pandey commented on HDDS-638:
-------------------------------------------
#
{quote} final File snapshotFile = snapshot.getFile().getPath().toFile();
{quote}We could make snapshotFile an attribute of state machine.
# In {{loadSnapshot}} we are loading term index, not the applied transaction
index.
# In {{takeSnapshot}} it seems the patch just creates the snapshot file, but
doesn't write the applied index to it.
# Let's explicitly distinguish between applied txn index and term index, by
calling the former as appliedTxnIndex.
# Why do we need to tracking applied-term-index?
> enable ratis snapshots for HDDS datanodes
> -----------------------------------------
>
> Key: HDDS-638
> URL: https://issues.apache.org/jira/browse/HDDS-638
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.3.0
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Blocker
> Attachments: HDDS-638.001.patch
>
>
> Currently on a restart, a hdds datanode, starts applying log entries from the
> start of the log.
> This should can be avoided by taking a ratis snapshot to persist the last
> stable state and on restart the datanodes start applying log from that index.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
