sitecore - 如何在庞大的内容交付 webfarm 中维护 Sitecore Lucene 索引？

Question

我知道Lucene索引不能共享:

Sitecore keeps a local copy of the Lucene index in the file system of each instance and does not support sharing the indexes between instances.

是否可以在 CM 和 CD 之间xcopy Lucene 索引？

是否有其他方法或建议来维护 30 多个内容交付服务器中的索引？

更新:我完全意识到 CD 必须启动自己的索引更新。对于超过 30 台 CD 服务器，我想也许有一段时间并非所有 CD 服务器都具有相同的索引集。我担心由于某种原因，某些 CD 服务器中的索引会失败，并且跟踪原因/位置将是 hell 。这就是为什么试图发现是否存在某种替代方法，将索引维护在一个地方(某种共享)并基本上立即复制到所有 CD

Answer 1

您需要为 CM 和 CD 服务器 Web 数据库启用历史引擎。

请参阅《Sitecore 扩展指南》中的摘录。

To enable History Engine for a Sitecore database: In the web.config file, add the following section to the /configuration/sitecore/databases/database element, where id equals the name of the database:

<Engines.HistoryEngine.Storage>
  <obj type="Sitecore.Data.$(database).$(database)HistoryStorage, Sitecore.Kernel">
   <param connectionStringName="$(id)" />
   <EntryLifeTime>30.00:00:00</EntryLifeTime>
  </obj>
</Engines.HistoryEngine.Storage>
<Engines.HistoryEngine.SaveDotNetCallStack>false</Engines.HistoryEngine.SaveDotNetCallStack>

When a Sitecore item is changed, the Lucene indexes are updated immediately on the Sitecore instance where the change was made. On remote servers in a multi-server environment, the Lucene indexes are not updated immediately after an item is changed. The Lucene indexes are automatically updated after the interval that is defined in the web.config file, in the Indexing.UpdateInterval setting and with the minimum wait time between the two consequent updates defined in the Indexing.UpdateJobThrottle setting.

参见here