[ 
https://issues.apache.org/jira/browse/YARN-8184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yufei Gu updated YARN-8184:
---------------------------
    Description: ContainerLocalizer or ResourceLocalizationService will use the 
ReadWriteDiskValidator as its disk validator when it downloads files if we 
configure the yarn.nodemanger.disk-validator to ReadWriteDiskValidator's name. 
In that case, ReadWriteDiskValidator will create a metric item for each 
directory localized, which will be too many metrics. We should let 
ContainerLocalizer only use the basic disk validator.  (was: ContainerLocalizer 
will use the ReadWriteDiskValidator as its disk validator when it downloads 
files if we configure the yarn.nodemanger.disk-validator to 
ReadWriteDiskValidator's name. In that case, ReadWriteDiskValidator will create 
a metric item for each directory localized, which will be too many metrics. We 
should let ContainerLocalizer only use the basic disk validator.)

> Too many metrics if containerLocalizer/ResourceLocalizationService uses 
> ReadWriteDiskValidator
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-8184
>                 URL: https://issues.apache.org/jira/browse/YARN-8184
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Yufei Gu
>            Priority: Major
>
> ContainerLocalizer or ResourceLocalizationService will use the 
> ReadWriteDiskValidator as its disk validator when it downloads files if we 
> configure the yarn.nodemanger.disk-validator to ReadWriteDiskValidator's 
> name. In that case, ReadWriteDiskValidator will create a metric item for each 
> directory localized, which will be too many metrics. We should let 
> ContainerLocalizer only use the basic disk validator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to