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.

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

Getting allocated time left from a SingularityCE does not work #7177

Closed
aldbr opened this issue Aug 22, 2023 · 1 comment
Closed

Getting allocated time left from a SingularityCE does not work #7177

aldbr opened this issue Aug 22, 2023 · 1 comment
Labels
Milestone

Comments

@aldbr
Copy link
Contributor

aldbr commented Aug 22, 2023

There is currently no way to get the allocated time left from a SingularityCE because environment variables are not propagated from the host to the container as noted here:

https://github.com/DIRACGrid/DIRAC/blob/integration/src/DIRAC/Resources/Computing/SingularityComputingElement.py#L325

Elastic jobs might need to get access to the batch system type to compute the time left in order to avoid running out of time.
The batch system type is retrieved from the environment variables present in the host such as:

https://github.com/DIRACGrid/DIRAC/blob/integration/src/DIRAC/Resources/Computing/BatchSystems/TimeLeft/TimeLeft.py#L132-L139

I see different possibilities:

  • SingularityCE searches for a batch system jobID environment variable and includes it if present (probably the easiest way)
  • The pilot adds the batch system type and jobID to the local cfg file (might be cleaner)

Any opinion?

@aldbr aldbr added the Bug label Aug 22, 2023
@aldbr aldbr added this to the v8.0 milestone Aug 22, 2023
@fstagni
Copy link
Contributor

fstagni commented Aug 24, 2023

I would go for the 2nd option (The pilot adds the batch system type and jobID to the local cfg file). This is definitely cleaner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants