Fix flaky ResourceAwareTasksTests.testBasicTaskResourceTracking test

[ketanv3]

Description

The assertMemoryUsageWithinLimits method checks if the memory usage is within 5% (up to 200 KB) of the expected memory usage. This additional buffer is to account for the class loading overhead when new code is encountered at runtime. Over time, addition of new code paths has resulted in greater overhead. This PR bumps up the 200 KB limit to 500 KB.

Related Issues

Resolves #8213

Check List

• New functionality includes testing.
  • All tests pass
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/21375/
• CommitID: 26a05c3

[Poojita-Raj]

On #8213, this test failure seems hard to reproduce on local. How are we confident this change will resolve the issue on our agent nodes?

Currently this class suite is part of the retry classes - #8825 - We can merge in this change and monitor to see if any further failures occur for a fixed time period (~2 weeks) before we remove it from the list of retried classes.

[ketanv3]

@Poojita-Raj I can reliably reproduce the issue with this command:

./gradlew ':server:test' --tests "org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests" -Dtests.seed=3A623BD634D99A0D -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-KW -Dtests.timezone=Europe/Paris

This test fails due to the following reasons – (1) addition of new code paths have increased the class loading overhead, (2) the randomized test seed influences the test execution order in this suite, which in turn influences when the class loading overhead is incurred. Using a different seed, for example, may not fail the test.

[Poojita-Raj]

Thanks for clarifying @ketanv3 :) This PR lgtm!