mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Mazumdar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-5301) Add synchronous validation for all types of Calls.
Date Wed, 13 Jul 2016 18:06:20 GMT

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

Anand Mazumdar commented on MESOS-5301:
---------------------------------------

This can also benefit frameworks that try to subscribe after they have been removed from the
master. Currently, we send them an asynchronous {{Event::ERROR}} after sending them an {{OK}}
response that is really confusing for framework developers. 

> Add synchronous validation for all types of Calls.
> --------------------------------------------------
>
>                 Key: MESOS-5301
>                 URL: https://issues.apache.org/jira/browse/MESOS-5301
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Anand Mazumdar
>              Labels: mesosphere
>
> Currently, we do a best effort validation for all calls sent to the master from the scheduler
by invoking {{validation::scheduler::call::validate(call, principal)}}. This is a generic
validation helper for all calls. However, for more fine grained validation for a particular
call, we invoke the validation as part of the call handle itself.
> {code}
> Option<Error> validationError = roles::validate(frameworkInfo.role());
> {code}
> This in turn makes all validations asynchronous i.e. the framework gets them as {{Event::ERROR}}
events later. It would be good if such validations can be handled while processing the {{Call}}
message itself synchronously.



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

Mime
View raw message