[ https://issues.apache.org/jira/browse/HADOOP-18954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bence Kosztolnik updated HADOOP-18954: -------------------------------------- Description: As we can see in this [Yarn documentation|https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html] beans can represent Float values as NaN. These values will be represented in the JMX response JSON like: {noformat} ... "GuaranteedCapacity": NaN, ... {noformat} Based on the [JSON doc|https://www.json.org/] NaN is not a valid JSON token ( however some of the parser libs can handle it ), so not every consumer can parse values like these. To be able to parse NaN values, a new feature flag should be created. The new feature will replace the NaN values with 0.0 values. The feature is default turned off. It can be enabled with the *hadoop.http.jmx.nan-filter.enabled* config. was: As we can see in this [Yarn documentation|https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html] beans can represent Float values as NaN. These values will be represented in the JMX response JSON like: {noformat} ... "GuaranteedCapacity": NaN, ... {noformat} Based on the [JSON doc|https://www.json.org/] NaN is not a valid JSON token ( however some of the parser libs can handle it ), so not every consumer can parse values like these. To be able to parse NaN values, a new feature flag should be created. The new feature will replace the NaN values with null values. > Filter NaN values from JMX json interface > ----------------------------------------- > > Key: HADOOP-18954 > URL: https://issues.apache.org/jira/browse/HADOOP-18954 > Project: Hadoop Common > Issue Type: Improvement > Components: common > Reporter: Bence Kosztolnik > Assignee: Bence Kosztolnik > Priority: Major > > As we can see in this [Yarn > documentation|https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html] > beans can represent Float values as NaN. These values will be represented in > the JMX response JSON like: > {noformat} > ... > "GuaranteedCapacity": NaN, > ... > {noformat} > Based on the [JSON doc|https://www.json.org/] NaN is not a valid JSON token ( > however some of the parser libs can handle it ), so not every consumer can > parse values like these. > To be able to parse NaN values, a new feature flag should be created. > The new feature will replace the NaN values with 0.0 values. > The feature is default turned off. It can be enabled with the > *hadoop.http.jmx.nan-filter.enabled* config. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org