Bug 2165495
| Summary: | Placement scheduler is using too much resources | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Bipul Adhikari <badhikar> |
| Component: | odf-sizer-tool | Assignee: | Bipul Adhikari <badhikar> |
| Status: | CLOSED ERRATA | QA Contact: | Joy John Pinto <jopinto> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.12 | CC: | cblum, kramdoss, odf-bz-bot |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.13.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-21 15:23:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bipul Adhikari
2023-01-30 09:38:18 UTC
In the above example issue is: ``` the postgres workload is running on the same nodes as ODF, but it never leaves the first AZ thus instead of running on three nodes in total, it wants 4 nodes and leaves room on 2 nodes ``` Commit https://github.com/red-hat-storage/sizer/commit/06dbc9288669423ccfe562d9e03ea7ec51926575 Fixes Issues around excess resource consumption in the sizer tool for ODF Deployment. Is the status still new? I can see that ODF consumption is now better, but the linked commit only worked on RGW? I think you linked the wrong commit? Also the Postgres issue mentioned above is still present: ``` the postgres workload is running on the same nodes as ODF, but it never leaves the first AZ thus instead of running on three nodes in total, it wants 4 nodes and leaves room on 2 nodes ``` This has been fixed as seen on https://storage.googleapis.com/sizer.ocs.ninja/beta/index.html?state=6d3d0700f03babc8c959fbf869148d69 Moving to on_qa to indicate that. The two commits attached work on improving the scheduler and improving the ordering of the placement of resources. Asking @cblum to verify it once. looks good in the beta channel No doc texts required. No documentation are there for this product. RDT not applicable. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3742 |