[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover
[ https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-8424: -- Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73, Mesosphere Sprint 74 (was: Mesosphere Sprint 72, Mesosphere Sprint 73) > Test that operations are correctly reported following a master failover > --- > > Key: MESOS-8424 > URL: https://issues.apache.org/jira/browse/MESOS-8424 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Jan Schlicht >Assignee: Jan Schlicht >Priority: Major > Labels: mesosphere > Fix For: 1.6.0 > > > As the master keeps track of operations running on a resource provider, it > needs to be updated on these operations when agents reregister after a master > failover. E.g., an operation that has finished during the failover should be > reported as finished by the master after the agent on which the resource > provider is running has reregistered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover
[ https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avinash Sridharan updated MESOS-8424: - Fix Version/s: 1.6.0 > Test that operations are correctly reported following a master failover > --- > > Key: MESOS-8424 > URL: https://issues.apache.org/jira/browse/MESOS-8424 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Jan Schlicht >Assignee: Jan Schlicht >Priority: Major > Labels: mesosphere > Fix For: 1.6.0 > > > As the master keeps track of operations running on a resource provider, it > needs to be updated on these operations when agents reregister after a master > failover. E.g., an operation that has finished during the failover should be > reported as finished by the master after the agent on which the resource > provider is running has reregistered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover
[ https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avinash Sridharan updated MESOS-8424: - Shepherd: Benjamin Bannier > Test that operations are correctly reported following a master failover > --- > > Key: MESOS-8424 > URL: https://issues.apache.org/jira/browse/MESOS-8424 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Jan Schlicht >Assignee: Jan Schlicht >Priority: Major > Labels: mesosphere > > As the master keeps track of operations running on a resource provider, it > needs to be updated on these operations when agents reregister after a master > failover. E.g., an operation that has finished during the failover should be > reported as finished by the master after the agent on which the resource > provider is running has reregistered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover
[ https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-8424: -- Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73 (was: Mesosphere Sprint 72) > Test that operations are correctly reported following a master failover > --- > > Key: MESOS-8424 > URL: https://issues.apache.org/jira/browse/MESOS-8424 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Jan Schlicht >Assignee: Jan Schlicht >Priority: Major > Labels: mesosphere > > As the master keeps track of operations running on a resource provider, it > needs to be updated on these operations when agents reregister after a master > failover. E.g., an operation that has finished during the failover should be > reported as finished by the master after the agent on which the resource > provider is running has reregistered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover
[ https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-8424: - Labels: mesosphere (was: ) > Test that operations are correctly reported following a master failover > --- > > Key: MESOS-8424 > URL: https://issues.apache.org/jira/browse/MESOS-8424 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Jan Schlicht >Assignee: Jan Schlicht >Priority: Major > Labels: mesosphere > > As the master keeps track of operations running on a resource provider, it > needs to be updated on these operations when agents reregister after a master > failover. E.g., an operation that has finished during the failover should be > reported as finished by the master after the agent on which the resource > provider is running has reregistered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover
[ https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Schlicht updated MESOS-8424: Sprint: Mesosphere Sprint 72 Story Points: 3 > Test that operations are correctly reported following a master failover > --- > > Key: MESOS-8424 > URL: https://issues.apache.org/jira/browse/MESOS-8424 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Jan Schlicht >Assignee: Jan Schlicht > > As the master keeps track of operations running on a resource provider, it > needs to be updated on these operations when agents reregister after a master > failover. E.g., an operation that has finished during the failover should be > reported as finished by the master after the agent on which the resource > provider is running has reregistered. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
