[jira] [Created] (MESOS-9298) Task failures sometimes can't be understood without looking into agent logs.

["Alexander Rukletsov (JIRA)" <ji...@apache.org>]

Alexander Rukletsov created MESOS-9298:
------------------------------------------

             Summary: Task failures sometimes can't be understood without looking into agent logs.
                 Key: MESOS-9298
                 URL: https://issues.apache.org/jira/browse/MESOS-9298
             Project: Mesos
          Issue Type: Epic
          Components: scheduler api
            Reporter: Alexander Rukletsov


Mesos communicates task state transitions via task status updates. They often include a reason, which aims to hint what exactly went wrong. However, these reasons are often:
- misleading
- vague
- generic.
Needless to say, this complicates triaging why the task has actually failed and hence is a bad user experience. The failures can come from a bunch of different sources: fetcher, isolators (including custom ones!), namespace setup, etc.

This epic aims to improve the UX by providing detailed, ideally typed, information about task failures.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)