You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The status_loop and work_loop of components calls check_drain_semaphore.
This seemed like a good idea before, but the way we run components makes this obsolete.
Generally:
We are running a component as a long-running daemon inside Kubernetes; the system can/will kill it at any time without providing a semaphore
We are running a component as a free-standing daemon on some host (i.e.: Bundlers on node007, c8-7, and c9-7); these are also killed without providing any semaphore
We are running the components as RUN_ONCE_AND_DIE as part of jobs at NERSC; these die after processing one unit of work and would not use the semaphore.
The text was updated successfully, but these errors were encountered:
The
status_loop
andwork_loop
of components callscheck_drain_semaphore
.This seemed like a good idea before, but the way we run components makes this obsolete.
Generally:
node007
,c8-7
, andc9-7
); these are also killed without providing any semaphoreRUN_ONCE_AND_DIE
as part of jobs at NERSC; these die after processing one unit of work and would not use the semaphore.The text was updated successfully, but these errors were encountered: