mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2735) Change the interaction between the slave and the resource estimator from polling to pushing
Date Mon, 18 May 2015 19:35:00 GMT

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

Jie Yu commented on MESOS-2735:
-------------------------------

Sorry that I just notice this reply here. I committed the patch already, but we can certainly
revert it if you have strong opinion against it.

> If the estimator never updates the "last estimate" in the slave, is the same effect -
no?

Not the same effect. The slave won't be blocked at least in the push model, meaning that the
slave will still be able to process all messages (e.g., runTask). In the polling model, a
bad resource estimator can block slave's event queue.

> Is the problem, that the current design doesn't support the "multiple firing" problem,
where the estimator updates while the callback is being executed?

Could you please elaborate on the "multiple firing" problem? I am curious what example in
your mind that makes you think that a push model is hard to use than the polling model.

> Change the interaction between the slave and the resource estimator from polling to pushing

> --------------------------------------------------------------------------------------------
>
>                 Key: MESOS-2735
>                 URL: https://issues.apache.org/jira/browse/MESOS-2735
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>              Labels: twitter
>
> This will make the semantics more clear. The resource estimator can control the speed
of sending resources estimation to the slave.
> To avoid cyclic dependency, slave will register a callback with the resource estimator
and the resource estimator will simply invoke that callback when there's a new estimation
ready. The callback will be a defer to the slave's main event queue.



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

Mime
View raw message