澄清Azure Web App规模实例 [英] Clarification on Azure Web App Scale Instance
问题描述
网络应用下方的每篇文章都可以选择自动缩放或手动缩放: https://azure.microsoft.com/zh-我们/文档/文章/见解如何扩展/
Per article below web app has an option to either auto or manual scale: https://azure.microsoft.com/en-us/documentation/articles/insights-how-to-scale/
如果能在下面得到澄清，将不胜感激:
Would appreciate if I can get clarification on below:
场景: 我有ASP.NET Sitecore CMS，它在后台使用Lucene进行搜索. Lucene索引会在发布新页面时重建.
Scenario: I've ASP.NET Sitecore CMS which uses Lucene behind the scene for search. Lucene index gets rebuilt upon publish of new pages.
假设我手动或自动缩放到2个实例:
Lets say I manually or auto scale to 2 instances:
-
幕后到底发生了什么，即将所有网站文件夹复制到新VM并设置IIS等?
What exactly happens behind the scene i.e. copies all the website folder to new VM and sets up IIS etc?
Web应用程序具有FTP和查看网站文件夹的功能.是否可以通过FTP传输到这两个实例?据我所知，我只能通过FTP传输到其中之一.
Web App has functionality to FTP and view website folders. Is it possible to FTP to both of these instances? From what I know I can only FTP to one of them.
更新:
我们面临的问题:
我们将lucene索引用于我们的Web应用程序.索引似乎建立在一个Web应用程序上，而不是建立在其他Web应用程序上(该网站对某些用户有效，而对其他用户无效).我们希望通过FTP或RDP进行确认，以确保确实如此.
We use lucene index for our web applications. Looks like the index is built on one web app and not other (website works for some user and not for others). We would like to FTP or RDP and see to make sure this is the case.
谢谢.
推荐答案
我们在具有多个实例的Web Apps上使用了一次Lucene.那时我们所做的是使用Azure Blob存储来保留索引文件，无论实例数量如何，所有文件都具有相同的索引信息. 唯一的问题是，当出现新实例(自动缩放)时，它们必须将索引加载到内存中，这会导致一些冷启动.
We used once Lucene on Web Apps with multiple instances. What we did back then was use Azure Blob Storage to keep the index files, no matter the number of instances, all had the same index information. The only problem was that when new instances would come up (autoscale), they had to load the index on memory and that lead to some cold-starts.
此后，我们移至 Azure搜索，并且从不回头:)
We moved to Azure Search afterwards and never looked back :)
这篇关于澄清Azure Web App规模实例的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
