[
https://issues.apache.org/jira/browse/MESOS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaojin CAO updated MESOS-4246:
------------------------------
Comment: was deleted
(was: [~Kennan]yes, just as [~gyliu] said. here is how k8s handle task failure:
1. k8s scheduler received task failure message, and update the task/pod status
in registry:
https://github.com/kubernetes/kubernetes/blob/master/contrib%2Fmesos%2Fpkg%2Fscheduler%2Fcomponents%2Fframework%2Fframework.go#L458
2. the replication controller will keep an eye on all tasks/pods, and will
create new pod instead of the failure one.)
> mesos support container application HA
> ---------------------------------------
>
> Key: MESOS-4246
> URL: https://issues.apache.org/jira/browse/MESOS-4246
> Project: Mesos
> Issue Type: Story
> Components: docker
> Affects Versions: 0.25.0
> Environment: we have setup one mesos cluster, one Master Node, and
> several Slave Node.
> Reporter: wangqun
> Priority: Critical
> Fix For: 0.25.0
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> Right now, we have setup one mesos cluster, one Master Node, and several
> Slave Nodes,
> We found that seems mesos not support slave nodes app reschudeling , for
> example a simple user case:
> 1. I have several containers running on one Slave Node.
> 2. The slave node down for some issue
> How can use those containers ? Could those containers rescheduled to other
> Slave Nodes ?
> From our test, it seems Mesos Not support this feature. Which means, users
> can not use those containers anymore.
> Could any Mesos developers confirmed that ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
