You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Lokesh Jain (Jira)" <ji...@apache.org> on 2021/06/14 05:56:00 UTC
[jira] [Commented] (HDDS-5289) updateDeleteTransactionId need not
be persisted into DB
[ https://issues.apache.org/jira/browse/HDDS-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362717#comment-17362717 ]
Lokesh Jain commented on HDDS-5289:
-----------------------------------
I thought the conversation was related to largest recorded transaction in SCM. The PR clears the changes required.
I think transactionId should be updated and maintained in ContainerInfo. Earlier this transactionId was updated when block deleting service sent these transactions to datanodes. I think it should either be replicated via Ratis or transaction update should be done when SCM receives transactions from OM. Second approach would require some changes.
> updateDeleteTransactionId need not be persisted into DB
> ---------------------------------------------------------
>
> Key: HDDS-5289
> URL: https://issues.apache.org/jira/browse/HDDS-5289
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM HA
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Labels: pull-request-available
>
> cc ~ [~glengeng]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org