You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/12/21 09:54:00 UTC

[jira] [Commented] (HDDS-1143) Ensure stateMachineData to be evicted only after writeStateMachineData completes in ContainerStateMachine cache

    [ https://issues.apache.org/jira/browse/HDDS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650696#comment-17650696 ] 

mingchao zhao commented on HDDS-1143:
-------------------------------------

Ozone 1.3.0 had been released and we currently have more than 600 open issues targeted for 1.3.0. I am moving the target field to 1.4.0.

If there is anything needs to be discussed about the Target Version, Please reach out to me via Apache email or Slack.

> Ensure stateMachineData to be evicted only after writeStateMachineData completes in ContainerStateMachine cache
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-1143
>                 URL: https://issues.apache.org/jira/browse/HDDS-1143
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Datanode
>    Affects Versions: 0.4.0
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>              Labels: TriagePending
>
> Currently, when we write StateMachineData, we first write to cache followed by write to disk. The entry in the cache can get evicted while the actual write is happening in case write is very slow. The purpose of this Jira is to ensure the cache eviction only after writeChunk completes.



--
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