Opened 5 years ago

Last modified 5 years ago

#6033 new enhancement

The list of hosts updates itself too slowly

Reported by: minondoa Owned by: minondoa
Priority: major Milestone: DRM4G-X.X.X
Component: DRM4G Keywords: drm4g, hosts,
Cc: carlos

Description

For example, if you destroy a VM and right after you submit some jobs, it will also "send" them to the VM you just deleted, because it still sees it as accessible in the hosts list (you can check this list by running "drm4g host list"). It will appear when doing "drm4g job list", that the non-existent VM is being used to execute the jobs. They won't get done for obvious reasons and they won't be reassigned to another available resource until much later.

Change History (1)

comment:1 Changed 5 years ago by minondoa

  • Milestone set to DRM4G-X.X.X

Doesn't seem to be possible.
Instead we might try to add way in which the DRM4G will ignore this already deleted resources.

Note: See TracTickets for help on using tickets.