[jira] [Commented] (MESOS-8419) RP manager incorrectly setting framework ID leads to CHECK failure

["Greg Mann (JIRA)" <ji...@apache.org>]

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

Greg Mann commented on MESOS-8419:
----------------------------------

Review here: https://reviews.apache.org/r/65034/

> RP manager incorrectly setting framework ID leads to CHECK failure
> ------------------------------------------------------------------
>
>                 Key: MESOS-8419
>                 URL: https://issues.apache.org/jira/browse/MESOS-8419
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>            Reporter: Greg Mann
>            Priority: Blocker
>              Labels: mesosphere
>
> The resource provider manager [unconditionally sets the framework ID|https://github.com/apache/mesos/blob/3290b401d20f2db2933294470ea8a2356a47c305/src/resource_provider/manager.cpp#L637] when forwarding operation status updates to the agent. This is incorrect, for example, when the resource provider [generates OPERATION_DROPPED updates during reconciliation|https://github.com/apache/mesos/blob/3290b401d20f2db2933294470ea8a2356a47c305/src/resource_provider/storage/provider.cpp#L1653-L1657], and leads to protobuf errors in this case since the framework ID's required {{value}} field is left unset.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)