[
https://issues.apache.org/jira/browse/MESOS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072571#comment-15072571
]
Guangya Liu commented on MESOS-4246:
------------------------------------
You can achieve HA in different ways with Kubernetes and Marathon.
For Kubernetes, you can create a replication controller and if one host with
pod is down, the replication controller manager will help restart a new pod to
make sure the pod number is same as what you defined in rc yaml template.
For Marathon, if you kill one task from Marathon task from Marathon dashboard,
Marathon will restart a new task.
You can always check log to see what is wrong.
> 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)
