You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2021/11/30 08:14:00 UTC

[jira] [Commented] (HDDS-6053) Fix too short container scrubber data scan interval.

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

Attila Doroszlai commented on HDDS-6053:
----------------------------------------

[~markgui], the scrubber should not be a heavy read load, as it can be (and is, by default) throttled (max. bytes per second).  If there are lots of big containers, scan interval would not be the limiting factor.  Do you have results that show it uses more bandwidth than configured?

> Fix too short container scrubber data scan interval.
> ----------------------------------------------------
>
>                 Key: HDDS-6053
>                 URL: https://issues.apache.org/jira/browse/HDDS-6053
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Mark Gui
>            Assignee: Mark Gui
>            Priority: Minor
>              Labels: pull-request-available
>
> I've found that the datanode container data scrubber defaults to have an scan interval if 1minute:
> {code:java}
> // ContainerScrubberConfiguration.java
> @Config(key = "data.scan.interval",
>     type = ConfigType.TIME,
>     defaultValue = "1m", 
> ...{code}
> It is too short since data scan is a heavy read load which may make normal IO slow,
> so a longer interval should be used as default, for example 1d.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org