Merge pull request #5826 from RainbowMango/pr_update_purge_mode
Update application failover purge mode comments
This commit is contained in:
commit
e0d77eb330
|
@ -259,13 +259,19 @@ type SuspendClusters struct {
|
||||||
ClusterNames []string `json:"clusterNames,omitempty"`
|
ClusterNames []string `json:"clusterNames,omitempty"`
|
||||||
}
|
}
|
||||||
|
|
||||||
// PurgeMode represents that how to deal with the legacy applications on the
|
// PurgeMode represents how to deal with the legacy application on the
|
||||||
// cluster from which the application is migrated.
|
// cluster from which the application is migrated.
|
||||||
type PurgeMode string
|
type PurgeMode string
|
||||||
|
|
||||||
const (
|
const (
|
||||||
// Immediately represents that Karmada will immediately evict the legacy
|
// Immediately represents that Karmada will immediately evict the legacy
|
||||||
// application.
|
// application. This is useful in scenarios where an application can not
|
||||||
|
// tolerate two instances running simultaneously.
|
||||||
|
// For example, the Flink application supports exactly-once state consistency,
|
||||||
|
// which means it requires that no two instances of the application are running
|
||||||
|
// at the same time. During a failover, it is crucial to ensure that the old
|
||||||
|
// application is removed before creating a new one to avoid duplicate
|
||||||
|
// processing and maintaining state consistency.
|
||||||
Immediately PurgeMode = "Immediately"
|
Immediately PurgeMode = "Immediately"
|
||||||
// Graciously represents that Karmada will wait for the application to
|
// Graciously represents that Karmada will wait for the application to
|
||||||
// come back to healthy on the new cluster or after a timeout is reached
|
// come back to healthy on the new cluster or after a timeout is reached
|
||||||
|
|
Loading…
Reference in New Issue