You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ivan Andika (Jira)" <ji...@apache.org> on 2025/01/03 10:51:00 UTC
[jira] [Commented] (HDDS-12008) Handle ContainerStateMachine#truncate for Streaming Write Pipeline
[ https://issues.apache.org/jira/browse/HDDS-12008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909547#comment-17909547 ]
Ivan Andika commented on HDDS-12008:
------------------------------------
[~szetszwo] I have a few related questions:
* In Ratis Async Pipeline, PutBlock is only done when the log entry is to be applied in StateMachine#applyTransactions. However, seems in Streaming Write Pipeline, the PutBlock is called in ContainerStateMachine#link, which is under WriteLog. Meaning that PutBlock might never be committed if the log is truncated. May I know whether it is correct to call trigger PutBlock ContainerStateMachine#link?
** Maybe it's better to handle it in StateMachine#applyTransaction triggered by sendForward. However, I'm not entirely sure whether StateMachine#applyTransaction will be triggered as part of sendForward.
* Any possible ideas regarding the truncation logic of a "linked" LogEntry? Do we need to delete the files, etc?
> Handle ContainerStateMachine#truncate for Streaming Write Pipeline
> ------------------------------------------------------------------
>
> Key: HDDS-12008
> URL: https://issues.apache.org/jira/browse/HDDS-12008
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Priority: Major
>
> StateMachine#link is called in WriteLog. Meaning that there might be a chance that the log entry will be truncated (e.g. INCONSISTENCY, etc). We need to see whether we should handle the ContainerStateMachine#truncate logic for Streaming Write Pipeline.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org