[
https://issues.apache.org/jira/browse/MESOS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181724#comment-15181724
]
Guangya Liu commented on MESOS-4870:
------------------------------------
Does the {{stderr}} in sandbox can help? The {{stderr}} can always give some
very detailed message for why the task failed.
> As a developer I WANT Mesos to provide a channel for richly structured error
> messages to surface from events like TASK_FAILED
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-4870
> URL: https://issues.apache.org/jira/browse/MESOS-4870
> Project: Mesos
> Issue Type: Improvement
> Reporter: James DeFelice
> Labels: external-volumes, mesosphere
>
> For example, a storage module attempts to mount a volume into my task's
> container. The mount operation fails because the file system driver required
> by the volume type isn't available on the host. Mesos generates a TASK_FAILED
> event and passes along the failure message generated by the module.
> If I'm LUCKY then the module populates the failure message with some text
> that explains the nature of the problem and the rich Mesos console that I'm
> using surfaces the nicely formatted text message.
> If I'm UNLUCKY then the module populates the failure message with something
> cryptic that doesn't help me understand what went wrong at all. I'm left with
> little context with which to troubleshoot the problem and my rich Mesos
> console can't help because there's very little additional context that
> shipped with the TASK_FAILED event.
> What I WANT is additional context so that my rich Mesos console can offer
> features like:
> a) tell me which subsystem/module failed (subsystem="storage",
> modulename="libfoobaz") and subsystem-specific details (storageprovider="foo"
> providerversion=0.1)
> b) provide an OS process details:
> i) the OS command line that failed
> ii) the UID of the process that failed
> iii) the GID of the process that failed
> iv) the environment of the command line that failed
> v) the error code that the process exited with
> c) how many time this type of error has happened, for this (or other)
> frameworks, and when
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
