New Glideins When Frontend Job Queue is Empty #443
Labels
BUG
For BUGS
factoryops
Factory Operations stakeholder
frontend
for affected component
hepcloud
HEPCloud stakeholder
Medium
Medium priority
rel:3.11.0
Release label for v3.11.0
Describe the bug
After setting up a container environment with GlideinWMS v3.11.0.rc2 (development series) to test the credentials refactoring module, it was observed that when the Frontend has completed running the submitted jobs and there are no more jobs in the Frontend queue, there are new Glideins being requested in the Factory. This continues to be the case until the
glideclient
classad expires. In contrast, this behavior is not being observed in my development environment (running GlideinWMS v3.10.7).To Reproduce
Upgrade existing installation of GlideinWMS to 3.11.0.rc2.
Expected behavior
No new glideins should be requested or created in the factory when there are no jobs submitted in the frontend queue.
Screenshots
Did some basic investigation following Marco Mambelli's suggestions to understand whether the problem was on the Factory or Frontend side. Here's the report:
Before submitting jobs:
After submitting jobs:
After jobs were completed:
When I saw a new glidein created in the factory:
Info (please complete the following information):
Stakeholders and components can be a comma-separated list or on multiple lines.
If you add a new stakeholder or component, not on the sample list, add it on a line on its own.
Additional context
Add any other context or supporting files about the problem here.
The text was updated successfully, but these errors were encountered: