Workers

Lifecycle

A worker in this state is registered with the cluster and ready to start running containers and storing volumes.

A worker in this state was previously registered with the cluster, but stopped advertising itself for some reason. Ususally this is due to network connectivity issues, or the worker stopping unexpectedly.

If the worker remains in this state and cannot be recovered, it can be removed using the prune-worker command.

The concourse land-worker command will put a worker in the LANDING state to safely drain its assignments for temporary downtime.

The ATC will wait for builds on the worker for jobs which aren't interruptible to finish, and transition the worker into LANDED state.

A worker in this state has successfully waited for all non-interruptible jobs on it after having concourse land-worker called. It will no longer be used to schedule any new containers or create volumes until it registers as RUNNING again.

The concourse retire-worker command will put a worker in the RETIRING state to remove it from the cluster permanently.

The ATC will wait for builds on the worker for jobs which aren't interruptible to finish, and remove the worker.