SOLR 搜索提供商的 Sitecore 8.1 索引重建策略 [英] Sitecore 8.1 index rebuild strategy for SOLR search provider

问题描述

只是通读了下面的索引更新策略文档，但无法得到关于哪种策略最适合 SOLR 搜索实施的明确答案:

Just read through the index update strategies document below but couldn't get the clear answer on which strategy is best for SOLR search implementation:

https://doc.sitecore.net/sitecore_experience_platform/search_and_indexing/index_update_strategies

我们已经设置了 master 和 slave Solr 端点，其中 master 将用于创建/更新.和奴隶只读.

We have setup the master and slave Solr endpoints where master will be used for create/update. And slave for reading only.

感谢您能否建议用于以下目的的索引策略:

Appreciate if you could suggest the indexing strategy to be used for:

1. 内容创作

1. Content Authoring

内容交付

解决方案托管在 azure 网络应用程序中，内容交付可以随时从 1-N 个数字扩大或缩小.

Solution is hosted in azure web apps and content delivery can be scaled up or down from 1-N number at any time.

我打算配置如下:

1. 只有 CA 有 OnPublishEndAsync
2. 所有 CD 都没有任何索引策略.

感谢您能否提出对您有用的解决方案.还有我们如何禁用索引策略?

Appreciate if you could suggest a solution that has worked for you. Also how do we disable indexing strategy?

谢谢.

推荐答案

通常在Solr(主+从Solr服务器)中使用replication时，应该这样配置:

Usually when you use replication in Solr (master + slave Solr servers), it should be configured like that:

内容创作(CM 服务器):

• 连接到 Solr 主服务器.
• 它为master 数据库运行syncMaster 策略，为web 数据库运行onPublishEndAsync 策略.

• connects to Solr master server.
• It runs syncMaster strategy for master database, and onPublishEndAsync for web database.

内容交付(CD 服务器):

• 连接到 Solr 从属服务器(如果有多个 Solr 从属服务器，则连接到某个负载均衡器).
• 已将所有索引策略设置为 manual - 他们不应该更新 Slave solr 服务器.

• connects to Solr slave server (or to some load balancer if there are multiple Solr slave servers).
• has all the indexing strategies set to manual - they should NEVER update Slave solr servers.

使用此解决方案，CD 服务器始终可以从 Solr 获取结果，即使正在进行完整的索引重建(这发生在 Master Solr 服务器上并且数据被复制到 Slaves 之后它完成了).

With this solution, CD servers always can get results from Solr, even if there is full index rebuild in progress (this happens on Master Solr server and data is copied to Slaves after it's finished).

您应该考虑为它们配备 2 个 Solr Slave 服务器和负载均衡器.如果你这样做:

You should think about having 2 Solr Slave servers and load balancer for them. If you do this:

• 如果 Solr master 由于某种原因关闭，slaves 仍会响应来自 CD 盒的请求.您可以安全地重新启动 master，重新编制索引，但唯一丢失的是您有一段时间没有在 CD 上获得 100% 最新的搜索结果.
• 如果 Solr slave 服务器之一出现故障，第二个 slave 服务器仍会响应请求，负载均衡器应将所有流量重定向到 slave 工作的服务器.

• If Solr master is down for some reason, slaves still answers to requests from CD boxes. You can safely restart master, reindex, and the only thing you lost is that you didn't have 100% up to date search results on CD for some time.
• If one of the Solr slave servers is down, second slave server still answers to the request and load balancer should redirect all the traffic to the slave server which works.

这篇关于SOLR 搜索提供商的 Sitecore 8.1 索引重建策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！