[
https://issues.apache.org/jira/browse/HDDS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650248#comment-17650248
]
mingchao zhao commented on HDDS-4666:
-------------------------------------
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.
> Handling disk issues in Datanodes
> ---------------------------------
>
> Key: HDDS-4666
> URL: https://issues.apache.org/jira/browse/HDDS-4666
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Attachments: Hdds datanode disk(volume) handling issues.pdf
>
>
> Currently, there is no notion of reserved space on datanodes as it exists on
> hdfs datanodes. Similarly, a datanode low on disk capacity continues to
> participate in pipeline allocation activity and keep on receiving write
> requests and these requests fail and potentially will end up running into
> retry loop in the client.
> Similarly, ratis log disks are currently not accounted for by disk checker.
> Once a ratis disk gets full, existing pipelines can not be closed as closing
> of pipeline involves taking a ratis snapshot which will not succeed if the
> ratis disk is full. Similarly, new pipelines cannot be functional on such
> disks and will end up failing write requests and contribute in client retry
> chain.
> Similarly, nodes low on disk capacity should not be choosen as targets for
> container re-replication.
> The goal of the Jira is address disk related issues on datanodes holistically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
