Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Increase CPU required by the OpenShift connector plugin #20763

Closed
l0rd opened this issue Nov 11, 2021 · 3 comments
Closed

Increase CPU required by the OpenShift connector plugin #20763

l0rd opened this issue Nov 11, 2021 · 3 comments
Labels
area/hosted-che area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Nov 11, 2021

Is your enhancement related to a problem? Please describe

The OpenShift Connector plugin takes a long long time to start. I looked a the CPU consumption and it looked like it was using all the 500 milicores available. I increased the the CPU limit in the devfile to 1000 milicores and the problem disappeared.

Curiously I tried to reproduce it on hosted Che and the OpenShift connector loads fast. I looked at the resources monitor and the used CPU was more than the CPU limit. How is that possible?

image

Describe the solution you'd like

Increase the CPU limit of the OpenShift connector.

Figure out why a plugin CPU is not limited on hosted Che.

Describe alternatives you've considered

No response

Additional context

No response
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 11, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 11, 2021
@svor
Copy link
Contributor

svor commented Nov 12, 2021

partially was fixed by eclipse-che/che-plugin-registry#1082

The problem why a plugin CPU is not limited should be investigated

@svor svor added area/plugin-registry severity/P2 Has a minor but important impact to the usage or development of the system. labels Nov 12, 2021
@ScrewTSW ScrewTSW added area/hosted-che severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. severity/P2 Has a minor but important impact to the usage or development of the system. labels Nov 12, 2021
@ScrewTSW
Copy link
Member

Also added area/hosted-che and bumped up the severity because of the resource quota iisue

@l0rd
Copy link
Contributor Author

l0rd commented Nov 15, 2021

I have tested on nightly Che and it works as expected. I have created as separate issue for the second problem (used CPU is higher than limit on developer sandbox). I am closing this issue as for me the main problem is solved. @ScrewTSW please re-open if you need to keep this issue opened until its fixed on Developer sandbox.

@l0rd l0rd closed this as completed Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/hosted-che area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@l0rd @svor @ScrewTSW @che-bot