You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/03/21 04:35:43 UTC
[jira] [Updated] (AURORA-189) Scheduler should log responses in
addition to requests
[ https://issues.apache.org/jira/browse/AURORA-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Farner updated AURORA-189:
-------------------------------
Labels: newbie (was: )
> Scheduler should log responses in addition to requests
> ------------------------------------------------------
>
> Key: AURORA-189
> URL: https://issues.apache.org/jira/browse/AURORA-189
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: David Robinson
> Priority: Minor
> Labels: newbie
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)