Integrate IO Based AdmissionController to AdmissionControl Framework

[ajaymovva]

Description

Integrated IO Based AdmissionController to AdmissionControl Framework.

• If IO usage percent is breached the threshold we are applying admission controller and start rejecting requests till it back to normal.
• IO Usage Calculation Based on Integrate IO Usage Tracker to the Resource Usage Collector Service and Emit IO Usage Stats #11880
• IO Based AdmissionControl is only available for Linux OS.

Node Stats Output On Linux

"admission_control": {
    "global_io_usage": {
        "transport": {
            "rejection_count": {
                "search": 8
            }
        }
    },
    "global_cpu_usage": {
        "transport": {
            "rejection_count": {}
        }
    }
}

Node Stats Output On Mac

"admission_control": {
    "global_cpu_usage": {
        "transport": {
            "rejection_count": {
                "search": 4
            }
        }
    }
}

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

• [RFC] Admission Controller framework for OpenSearch #8910
• [META] Admission Controller Framework #9504

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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]

Compatibility status:

Checks if related components are compatible with change 4626c01

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/performance-analyzer.git]

[github-actions]

❌ Gradle check result for e551547: 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]

❌ Gradle check result for b0f31ea: 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]

❌ Gradle check result for 93ee481: 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]

❌ Gradle check result for 7a0519c: 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]

❕ Gradle check result for d6c1b85: UNSTABLE

• TEST FAILURES:

      1 org.opensearch.search.SearchWeightedRoutingIT.testMultiGetWithNetworkDisruption_FailOpenEnabled

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

Attention: Patch coverage is 83.60656% with 10 lines in your changes are missing coverage. Please review.

Project coverage is 71.33%. Comparing base (b15cb0c) to head (4626c01).
Report is 24 commits behind head on main.

Files	Patch %	Lines
...ontrol/controllers/IoBasedAdmissionController.java	81.81%	3 Missing and 3 partials ⚠️
...ting/admissioncontrol/AdmissionControlService.java	60.00%	0 Missing and 2 partials ⚠️
...ode/resource/tracker/NodeResourceUsageTracker.java	50.00%	0 Missing and 1 partial ⚠️
...l/settings/IoBasedAdmissionControllerSettings.java	95.23%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #12583      +/-   ##
============================================
- Coverage     71.42%   71.33%   -0.09%     
- Complexity    59978    60017      +39     
============================================
  Files          4985     4988       +3     
  Lines        282275   282490     +215     
  Branches      40946    40980      +34     
============================================
- Hits         201603   201504      -99     
- Misses        63999    64253     +254     
- Partials      16673    16733      +60     

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

[andrross]

FYI, your changelog entry is in the wrong section, hence the cherry-pick failure on the backport.