7d7d2f9f2a
We can obtain the same information from the SQL database now, so do that and remove the filesystem-based time database. This will help support multiple schedulers (as they will all have access to the same data). Nothing in the scheduler uses the state directory anymore, so clean up the docs around that. The executor still has a state dir where it may install ansible-related files. The SQL query was rather slow in practice because it created a temporary table since it was filtering mostly by buildset fields then sorting by build.id. We can sort by buildset.id and get nearly the same results (equally valid from our perspective) much faster. In some configurations under postgres, we may see a performance variation in the run-time of the query. In order to keep the time estimation out of the critical path of job launches, we perform the SQL query asynchronously. We may be able to remove this added bit of complexity once the scale-out-scheduler work is finished (and/or we we further define/restrict our database requirements). Change-Id: Id3c64be7a05c9edc849e698200411ad436a1334d |
||
|---|---|---|
| .. | ||
| zuul-executor.service.d | ||
| zuul-scheduler.service.d | ||
| zuul-web.service.d | ||
| layout.yaml-sample | ||
| logging.conf-sample | ||
| zuul-executor.service | ||
| zuul-scheduler.service | ||
| zuul-web.service | ||
| zuul.conf-sample | ||