[jira] [Updated] (MESOS-2513) FrameworkID not set in FrameworkInfo sent to Slave as part of RunTaskMessage
[ https://issues.apache.org/jira/browse/MESOS-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-2513: -- Shepherd: (was: Adam B) > FrameworkID not set in FrameworkInfo sent to Slave as part of RunTaskMessage > > > Key: MESOS-2513 > URL: https://issues.apache.org/jira/browse/MESOS-2513 > Project: Mesos > Issue Type: Bug >Reporter: Kapil Arya >Assignee: Kapil Arya > Labels: mesosphere > > While working on creating the decorator/undecorator hooks we realized that in > one of our slave hooks, we receive a FrameworkInfo which doesn't have the > 'id' field set. As it turns out, the FrameworkInfo sent by Master to Slave as > part of the RunTaskMessage is missing the id as well. In fact, the Master > also sends a FrameworkID separately as part of the RunTaskMessage. > Why not modify the Master to always set 'id' in FrameworkInfo before sending > it with RunTaskMessage. Would this affect the correctness? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MESOS-2513) FrameworkID not set in FrameworkInfo sent to Slave as part of RunTaskMessage
[ https://issues.apache.org/jira/browse/MESOS-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2513: -- Shepherd: Adam B (was: Niklas Quarfot Nielsen) FrameworkID not set in FrameworkInfo sent to Slave as part of RunTaskMessage Key: MESOS-2513 URL: https://issues.apache.org/jira/browse/MESOS-2513 Project: Mesos Issue Type: Bug Reporter: Kapil Arya Assignee: Kapil Arya While working on creating the decorator/undecorator hooks we realized that in one of our slave hooks, we receive a FrameworkInfo which doesn't have the 'id' field set. As it turns out, the FrameworkInfo sent by Master to Slave as part of the RunTaskMessage is missing the id as well. In fact, the Master also sends a FrameworkID separately as part of the RunTaskMessage. Why not modify the Master to always set 'id' in FrameworkInfo before sending it with RunTaskMessage. Would this affect the correctness? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2513) FrameworkID not set in FrameworkInfo sent to Slave as part of RunTaskMessage
[ https://issues.apache.org/jira/browse/MESOS-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapil Arya updated MESOS-2513: -- Target Version/s: (was: 0.22.0) Shepherd: Niklas Quarfot Nielsen Assignee: Kapil Arya FrameworkID not set in FrameworkInfo sent to Slave as part of RunTaskMessage Key: MESOS-2513 URL: https://issues.apache.org/jira/browse/MESOS-2513 Project: Mesos Issue Type: Bug Reporter: Kapil Arya Assignee: Kapil Arya While working on creating the decorator/undecorator hooks we realized that in one of our slave hooks, we receive a FrameworkInfo which doesn't have the 'id' field set. As it turns out, the FrameworkInfo sent by Master to Slave as part of the RunTaskMessage is missing the id as well. In fact, the Master also sends a FrameworkID separately as part of the RunTaskMessage. Why not modify the Master to always set 'id' in FrameworkInfo before sending it with RunTaskMessage. Would this affect the correctness? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
