Fix NodeResourceUsageStats constructor to include nativeMemoryUtilizationPercent param

[GeekGlider]

Description

Fixes compilation error in tiered storage integration tests caused by PR #21191 which added a 6th parameter (nativeMemoryUtilizationPercent) to the NodeResourceUsageStats constructor. Updated the constructor calls in HotToWarmTieringServiceIT and WarmToHotTieringServiceIT to pass 0.0 for the new parameter.

Related Issues

Fixes compilation failure introduced by #21191

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

PR Reviewer Guide 🔍

(Review updated until commit da78ece)

Here are some key observations to aid the review process:

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

Latest suggestions up to da78ece
Explore these optional code suggestions:

Category	Suggestion	Impact
General	Use named constant for memory utilization The hardcoded 0.0 for nativeMemoryUtilizationPercent may not accurately represent test scenarios. Consider using a meaningful constant or variable that reflects the intended test behavior, especially since this test validates JVM utilization breach scenarios. server/src/internalClusterTest/java/org/opensearch/storage/tiering/HotToWarmTieringServiceIT.java [1048] -nodeId -> new NodeResourceUsageStats(nodeId, System.currentTimeMillis(), 99, 20, null, 0.0) +private static final double DEFAULT_NATIVE_MEMORY_UTILIZATION = 0.0; +... +nodeId -> new NodeResourceUsageStats(nodeId, System.currentTimeMillis(), 99, 20, null, DEFAULT_NATIVE_MEMORY_UTILIZATION) Suggestion importance[1-10]: 4 __ Why: While using a named constant could improve code readability, the suggestion has limited impact since 0.0 is a clear default value for native memory utilization in a test that focuses on JVM utilization breach. The improvement is marginal and mainly stylistic.	Low

---

Previous suggestions

Suggestions up to commit 34abae7

Category	Suggestion	Impact
General	Use named constant for memory utilization The hardcoded 0.0 for nativeMemoryUtilizationPercent may not accurately represent test scenarios. Consider using a meaningful constant or variable that reflects the intended test behavior, especially since this test validates JVM utilization breach scenarios. server/src/internalClusterTest/java/org/opensearch/storage/tiering/HotToWarmTieringServiceIT.java [1048] -nodeId -> new NodeResourceUsageStats(nodeId, System.currentTimeMillis(), 99, 20, null, 0.0) +private static final double DEFAULT_NATIVE_MEMORY_UTILIZATION = 0.0; +... +nodeId -> new NodeResourceUsageStats(nodeId, System.currentTimeMillis(), 99, 20, null, DEFAULT_NATIVE_MEMORY_UTILIZATION) Suggestion importance[1-10]: 4 __ Why: While using a named constant could improve code readability, the suggestion has limited impact since this is a test file where hardcoded values are common and acceptable. The 0.0 value is clear in context and doesn't significantly hinder understanding. The test focuses on JVM utilization (99%), not native memory utilization.	Low

[github-actions]

❌ Gradle check result for 34abae7: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit da78ece

[github-actions]

✅ Gradle check result for da78ece: SUCCESS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.46%. Comparing base (75b6e82) to head (da78ece).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #21714      +/-   ##
============================================
- Coverage     73.56%   73.46%   -0.10%     
- Complexity    74882    74885       +3     
============================================
  Files          5994     5997       +3     
  Lines        339592   339688      +96     
  Branches      48948    48961      +13     
============================================
- Hits         249811   249547     -264     
- Misses        69893    70307     +414     
+ Partials      19888    19834      -54     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.