澄清"Sticky to Slot"的含义.用于部署插槽 [英] Clarification on meaning of "Sticky to Slot" for deployment slots
问题描述
这是Azure SQL DB论坛上此帖子的后续内容
This is a followup on this post from Azure SQL DB forum
https://social.msdn.microsoft.com/Forums/zh-CN/7d712443-9bb7-48dc-b8dc-48377de69363/clarification-on-意义-of"sticky-to-slot" for-deployment-slots ?forum = ssdsgetstarted
https://social.msdn.microsoft.com/Forums/en-US/7d712443-9bb7-48dc-b8dc-48377de69363/clarification-on-meaning-of-quotsticky-to-slotquot-for-deployment-slots?forum=ssdsgetstarted
那里的回答准确地说明了我所询问的情况，即:
The response there accurately recounts an understanding of the situation I'm asking about, that is:
插槽包含一组应用程序文件.两个插槽可以包含稍有不同的应用程序文件版本，并且可以具有不同的连接字符串.
A slot contains a set of application files. Two slots can contain slightly different versions of the application files, and can have different connection strings.
在交换部署时隙期间，不会复制文件，只是DNS的指向不同.
During a deployment slot swap the files aren't copied, it's just the DNS's that are pointed differently.
因此，术语生产槽"是指确实意味着DNS指向的文件集，即使指向的实际物理插槽(即文件集)已更改.
So the term "production slot" really means the set of files that the DNS points to, even if the actual physical slot that is pointed to (i.e. set of files) is changed.
我的问题是，何时将连接字符串设置为对生产槽固定"，而将交换"设置为固定".发生时，生产连接字符串数据到底发生了什么?
My question is, when a connection string is made "sticky to the production slot", and the "swap" occurs, what exactly happens to the production connection string data?
1)是否将其复制到"new"文件中?生产版位，像真实文件副本一样? (似乎那样会混淆"两个不同文件集中的实际内容)
2)它是否指向"?来自新"生产版位(似乎不太可靠，因为可以编辑旧"生产版位)
3)Azure是否管理指向与应用程序代码文件分开的生产插槽的连接字符串的指针?
3.1)如果是，它是如何做到的?是否保留连接字符串数据的单独副本?如果是这样，如果真实的"数据库不可用，Azure如何更新该数据.连接字符串数据(可能已加密)发生了变化?
1) Is it copied to the "new" production slot, like a real file copy? (seems like that would 'confuse' what was actually in the two different file sets)
2) Is it "pointed to" from the "new" production slot (does not seem that would be reliable, because the "old" production slot could be edited)
3) Does Azure manage a pointer to the connection string for the production slot that is separate from the app code files?
3.1) If so, how does it do that? Does it keep a separate copy of the connection string data? If so, how does Azure update that data if the "real" connection string data (which might be encrypted) changes?
我相信这一切都能奏效.但是，在我围绕它构建程序之前，我想确切地了解它是如何工作的.因为看起来应用程序服务可能会因为做错而中断.
I believe this all works. However, I would like to know exactly how it works before I build my procedures around it. Because it seems like the applications service can get disrupted by doing it wrong.
任何对此的指导将不胜感激.
Any guidance on this would be appreciated.
谢谢！
推荐答案
codequestor-它不仅仅是在后台进行DNS交换 .也许，跟随可能会有所帮助?
应用程序服务交换行为讨论
Hi codequestor - It's a bit more than just DNS swap under the hood. Perhaps, following might help?
App services swap behavior discussion
这篇关于澄清"Sticky to Slot"的含义.用于部署插槽的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
