Description
The scheduler logs requests but not responses. This makes troubleshooting difficult because the logs show when a request was received (it can be inferred), one or many actions as a result of the request, but then nothing showing that the request has been responded to.
For example, if a user performs an update, X tasks will be killed before starting X new tasks. If killing X tasks exceeds a time limit (kill_task_max_backoff) a "Tasks were not killed in time" message is returned to the client, but the logs continue to show actions occurring as a result of the initial request.