如何在庞大的内容交付网络农场中维护Sitecore Lucene索引? [英] How to maintain Sitecore Lucene indexes in huge content delivery webfarm?

问题描述

我知道Lucene索引无法共享:

I know that Lucene indexes cannot be shared:

Sitecore在以下文件系统中保留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索引?

Is it possible to xcopy Lucene indexes between CM and CD?

还有其他方法或建议来在30多个内容交付服务器中维护索引吗?

Is there some other approach or recommendation to maintain a indexes in 30+ content delivery servers ?

更新: 我完全知道CD必须开始其自身的索引更新.我想拥有30台以上的CD服务器，也许会在一段时间内，并非所有CD服务器都具有相同的索引集.出于某种原因，我担心某些CD服务器中的索引将失败，并会跟踪为什么/在哪里.这就是为什么要尝试发现是否有其他方法可以将索引保留在一个位置(某种形式的共享)并基本上立即复制到所有CD

Update: I’m fully aware that CDs must kick off their own index update. With over 30 CD servers I’m thinking that maybe there will be a period of time that not all CD server have the same set of indexes. I’m afraid that for some reason the indexes will fail in some of the CD servers and tracking why/where will be hell. That’s why trying to discover if there some alternative approach where indexes are maintain in one place (some sort shared) and basically instantly replicated to all CD

推荐答案

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

You need to enable History Engine for the CM and CD servers web database.

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

See this extract from the Sitecore Scaling Guide.

要为Sitecore数据库启用历史记录引擎，请执行以下操作:在web.config中 文件，将以下部分添加到 /configuration/sitecore/databases/database元素，其中id等于 数据库名称:

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>

更改Sitecore项后，Lucene索引将更新 立即在进行更改的Sitecore实例上.在 多服务器环境中的远程服务器，Lucene索引是 更改项目后不会立即更新. Lucene索引 会在定义的时间间隔后自动更新 web.config文件，在Indexing.UpdateInterval设置中，并使用 两次后续更新之间的最短等待时间 Indexing.UpdateJobThrottle设置.

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.

请参见此处

这篇关于如何在庞大的内容交付网络农场中维护Sitecore Lucene索引?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！