Add safeguard limits for file cache during node level allocation

[kotwanikunal]

Description

• Related to Add safeguards to prevent file cache over-subscription #7713
• Adds safeguards to prevent file cache over-subscription during allocation for individual node level decisions.
• Fetches the filecache stats to get node cache size, calculates the remote shard size on nodes and verifies if the shard can be safely allocated to the said node
• size of shard + sum(remote shards on the node) < 5 * (node cache size)
• The constant value will be replaced by a setting in a following PR.

Related Issues

Resolves #7033

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• 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.

[kotwanikunal]

Tagging previous reviewers: @andrross / @reta / @Bukhtawar

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/18132/
• CommitID: 840d282

[codecov]

Codecov Report

Merging #8208 (d94f6a9) into main (418ab51) will increase coverage by 0.10%.
The diff coverage is 91.66%.

❗ Current head d94f6a9 differs from pull request most recent head f5ddcdc. Consider uploading reports for the commit f5ddcdc to get more accurate results

@@             Coverage Diff              @@
##               main    #8208      +/-   ##
============================================
+ Coverage     70.85%   70.96%   +0.10%     
+ Complexity    56948    56942       -6     
============================================
  Files          4758     4759       +1     
  Lines        269382   269224     -158     
  Branches      39414    39405       -9     
============================================
+ Hits         190877   191055     +178     
+ Misses        62429    62002     -427     
- Partials      16076    16167      +91     

Impacted Files	Coverage Δ
...search/index/store/remote/filecache/FileCache.java	72.05% <ø> (ø)
.../main/java/org/opensearch/cluster/ClusterInfo.java	59.42% <62.50%> (-0.13%)	⬇️
...opensearch/cluster/InternalClusterInfoService.java	75.53% <100.00%> (-1.02%)	⬇️
...uting/allocation/decider/DiskThresholdDecider.java	73.89% <100.00%> (+1.27%)	⬆️

... and 533 files with indirect coverage changes

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/18134/
• CommitID: 98e9df7

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/18394/
• CommitID: e190294

[kotwanikunal]

@reta Resolved your comments. 3 green gradle checks in a row might be a sign :)

[reta]

@reta Resolved your comments. 3 green gradle checks in a row might be a sign :)

@kotwanikunal my apologies, missed that somehow, will look first thing tomorrow morning

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication
      1 org.opensearch.remotestore.RemoteStoreRefreshListenerIT.testRemoteRefreshRetryOnFailure

• URL: https://build.ci.opensearch.org/job/gradle-check/19168/
• CommitID: d94f6a9
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.indices.replication.SegmentReplicationIT.testDropPrimaryDuringReplication

• URL: https://build.ci.opensearch.org/job/gradle-check/19657/
• CommitID: f5ddcdc
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8208-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 91bfa01606974b947455fbc289e21a1aad096fa8
# Push it to GitHub
git push --set-upstream origin backport/backport-8208-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8208-to-2.x.

[kotwanikunal]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8208-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 91bfa01606974b947455fbc289e21a1aad096fa8
# Push it to GitHub
git push --set-upstream origin backport/backport-8208-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8208-to-2.x.

Will look into the backport after the followup PR.