服务结构中的数据持久性和回滚升级策略 [英] Data persistence and roll back upgrade policy in service fabric

问题描述

大家好，

我有可靠的有状态和无状态应用程序服务结构.如果我要测试这些应用程序是在本地计算机集群中发布这些应用程序，但是每次都在删除现有应用程序并在本地创建新应用程序 簇.我丢失了之前添加的数据.

I have service fabric reliable stateful and stateless applications. If I want to test these applications am publishing those in my local machine cluster, But Every time it is removing existing application and creating a new application in the local cluster. I am losing my data which I have added earlier.

如何在我的应用程序中设置本地集群以进行升级和数据持久性.

How to set up my local cluster to upgrade and data persistence in my application.

任何人都可以提供所需的配置答复吗?

Can anyone give reply with the configuration needed for this?

SrinivasReddyVelpula

SrinivasReddyVelpula

推荐答案

如果在单个计算机上安装了开发集群，则需要查看其中显示的一些文档更新群集时:

Reviewing some of the documentation it appears if you have your development cluster setup on a single machine you need to rebuild the cluster when updating it: 

您可以升级自己的仅当您使用生产型节点配置(其中每个服务结构都在其中)时，才能群集到新版本 节点分配在单独的物理机或虚拟机上.如果您有一个开发群集，则在一台物理或虚拟机上有多个Service Fabric节点，则必须使用新版本重新创建群集.

You can upgrade your cluster to the new version only if you're using a production-style node configuration, where each Service Fabric node is allocated on a separate physical or virtual machine. If you have a development cluster, where more than one Service Fabric node is on a single physical or virtual machine, you must re-create the cluster with the new version.

您是否考虑过在推送更改之前从集群中提取所有可能需要的特定数据?

Have you considered pulling any specific data you might need off the cluster prior to pushing changes? 

这篇关于服务结构中的数据持久性和回滚升级策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！