[
https://issues.apache.org/jira/browse/YUNIKORN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343697#comment-17343697
]
Weiwei Yang commented on YUNIKORN-668:
--------------------------------------
YK did not persist any state in external storage, but it has some in-memory
state, during a restart, YK recovers its state from API server. This is the
resilience mode we are using today, read more here:
http://yunikorn.apache.org/docs/next/design/resilience. If you want to achieve
HA with hot-standby, that is not something supported today, that won't be very
easy to implement as well. Unless we see a really strong need for this. Anyway,
like [~yuchaoran2011] commented, today we can leverage the deployment restart
to handle the fail-over cases, that brings a small downtime but I think that
should be fine.
> There is no fail over mechanism in shim project.
> ------------------------------------------------
>
> Key: YUNIKORN-668
> URL: https://issues.apache.org/jira/browse/YUNIKORN-668
> Project: Apache YuniKorn
> Issue Type: New Feature
> Reporter: MichealShin
> Priority: Critical
>
> We want to have the fail over feature in the shim project, but can not work
> when just set the replication to 2 in k8s. The two pods just cannot work
> together . When pod 1 get the config, the pod 2 will not. To make it worse,
> the working pod may not work after some time, and the other will get the
> right config.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
