Skip to content

executor: do not initialize ressources in the constructor

Martin Roukala requested to merge executor_startup_reliability into master

When a client tries to run a new job, the executor server creates a job process, waits for the job process to expose its state via a unix socket, then returns the status code 200 to the client to indicate that the process went well.

The client will then wait up to 5 seconds for the job process to connect... which means that it is crucial for the job process to be ready to connect to the client as soon as it exposes its state via the unix socket.

Unfortunately, the current code starts doing some initialization that depend on network services... which may be down. This series fixes this!

Closes: #145 (closed)

Merge request reports