[HADOOP-18954] Filter NaN values from JMX json interface

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: common
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Bence Kosztolnik
• Reporter: Bence Kosztolnik
• Created: 26/Oct/23 09:41
• Updated: 15/Feb/24 09:30
• Resolved: 09/Nov/23 09:14

Description

As we can see in this Yarn documentation beans can represent Float values as NaN. These values will be represented in the JMX response JSON like:

...
"GuaranteedCapacity": NaN,
...

Based on the JSON doc 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.

Issue Links

• is related to: YARN-9563 Resource report REST API could return NaN or Inf
• is related to: YARN-1479 Invalid NaN values in Hadoop REST API JSON response
• relates to: YARN-11010 YARN ui2 hangs on the Queues page when the scheduler response contains NaN values
• links to: GitHub Pull Request #6229