chenyulin0719 opened a new pull request, #675: URL: https://github.com/apache/yunikorn-core/pull/675
### What is this PR for? Metric of releasedContainers will decrease twice if preemption was triggered. If a allocation was preempted, 2 RMReleaseAllocationEvent will be created as below: 1. Core → Shim (TerminationType: **PREEMPTED_BY_SCHEDULER**) 2. Core → Shim (TerminationType: **STOPPED_BY_RM**) (A callback of RM Shim → Core.) This PR skip the container decrease in first RMReleaseAllocationEvent. (Core → Shim, TerminationType: **PREEMPTED_BY_SCHEDULER**). ### What type of PR is it? * [x] - Bug Fix * [ ] - Improvement * [ ] - Feature * [ ] - Documentation * [ ] - Hot Fix * [ ] - Refactoring ### Todos NA ### What is the Jira issue? https://issues.apache.org/jira/browse/YUNIKORN-2025 ### How should this be tested? 1. Trigger e2e test 'Verify_basic_preemption'. (You will see -1 running conainer in YuniKorn UI.) 2. Redeploy YuniKorn with this fix 3. Trigger e2e test 'Verify_basic_preemption'. (You will see 0 running conainer in YuniKorn UI.) ### Screenshots (if appropriate) <img width="1449" alt="Nagative Running Container Count - UI Screenshot" src="https://github.com/apache/yunikorn-core/assets/26764036/2dd91049-e262-4d00-9332-329df73d79b4";> ### Questions: NA -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
