Sitecore 索引重建实践 [英] Sitecore index rebuilding practices

问题描述

在我们的 sitecore 项目(6.6.0 rev. 130404)中，我们有超过 200 万个 sitecore 项目.我们配置了几个 Lucene 索引(每个索引都是这些项目的一个子集).我们面临的问题是重新重建这些索引所需的时间.特别是使用 Sitecore 的快速搜索索引，除了我们的自定义索引之外，重建该索引可能需要将近一整天的时间.

In our sitecore project (6.6.0 rev. 130404), we have more than 2 million total sitecore items. We have several Lucene indexes (each for a subset of these items) configured. The issue we face is the time it takes to freshly rebuild these indexes. Specially with the Sitecore's QuickSearch index, it might take nearly a full day to rebuild that index, in addition to our custom indexes.

在日常运营中维护大型站点核心索引的通常做法是什么?您需要多久重建一次索引?当你这样做时，如何应对长时间的网站停机(索引重建使索引下线)?

What are the usual practices followed with maintenance of large sitecore indexes in day-to-day operations? How often would you need to rebuild indexes? and when you do, how to cope with long website down-time (index rebuilding makes the index offline)?

推荐答案

如果您有多个服务器，您可以从负载均衡器中取出其中一个(或阻止它以任何其他方式传递内容)并重建索引这台服务器.完成后，只需将其放回负载均衡器即可.

If you have multiple servers you can take out one of them from the load balancer (or stop it from delivering content in any other way) and rebuild the index on this server. While it's done, just put it back in load balancer.

您也可以尝试使用 Sitecore Lucene Refresher.

看看如何维护大型内容交付网络农场中的 sitecore lucene 索引 以获得更多选项.

Take a look at how to maintain sitecore lucene indexes in huge content delivery webfarm for more options.

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