-
Notifications
You must be signed in to change notification settings - Fork 294
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.
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
Master polling the oVirt API too frequently #110
Comments
OKD uses the same ovirt api controller as OCP, so perhaps we don't need a tracking bug in OKD. I don't mind keeping it open for tracking purposes though |
So I may have some additional information for this. I had forgotten that I had configured the session timeout within oVirt to be 1440 minutes instead of 30minutes. I've reduced this back to 30minutes and I haven't seen this issue reoccur. My view is that: What do you think? Should we keep this ticket as a feature request, or should that be a seperate ticket somewhere else? |
As an afterthought it might be worth also having a feature request to re-use an existing session token rather than hammering the API with new login requests. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi,
I have raised a bugzilla for the oVirt project for this too, but I noticed that the OKD service seems to poll the ovirt hosted-engine api very frequently (looks to be generating a new session every 5 seconds). This is having a knock-on effect of exposing a bug in oVirt which causes the hosted-engine to stop responding to API requests as it is unable to do GC fast enough, even on a high powered system.
The BZ is https://bugzilla.redhat.com/show_bug.cgi?id=1815271
The text was updated successfully, but these errors were encountered: