[jira] [Comment Edited] (MESOS-1955) Specification for Executor and Task life cycles in Slave

["Bernd Mathiske (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206210#comment-14206210 ] 

Bernd Mathiske edited comment on MESOS-1955 at 11/11/14 9:37 AM:
-----------------------------------------------------------------

Whereas MESOS-2068 is aiming at providing some useful documentation as soon as possible, MESOS-1955 will hopefully still be pursued to come up with a more thorough, formal specification - possibly even with some sort of a correctness proof. 



was (Author: bernd-mesos):
Whereas MESO-2068 is aiming at providing some useful documentation as soon as possible, MESOS-1955 will hopefully still be pursued to come up with a more thorough, formal specification - possibly even with some sort of a correctness proof. 


> Specification for Executor and Task life cycles in Slave
> --------------------------------------------------------
>
>                 Key: MESOS-1955
>                 URL: https://issues.apache.org/jira/browse/MESOS-1955
>             Project: Mesos
>          Issue Type: Documentation
>          Components: slave
>    Affects Versions: 1.0.0, 0.23.0
>         Environment: all
>            Reporter: Bernd Mathiske
>              Labels: documentation, quality, specification, testing
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> We should create a precise specification of what the Mesos source code is supposed to be implementing wrt. the life cycle of executors and tasks. And in addition, we should document why certain design decisions have been made one way or another, to provide guidance for future code changes.
> With such a source code-independent specification, we could write unbiased regression and scale tests, which would be instrumental in maintaining high quality.
> Furthermore, this would make the source code more amenable.
> Why pick this particular area of the source code? Shouldn't more of Mesos have a thorough specification? Probably so. But we need to start somewhere and this area seems to be a good choice, given both its intricacy and its importance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)