Skip to main content

Clearing Indexes on Sitecore Content Delivery Servers

For anyone that is building a website on Sitecore you have probably come across this issue. In even a basic production deployment of Sitecore you have a content management box and a content delivery box. When content is updated on the management servers you want your content delivery box’s indexes to be updated. Some people think you need to create your own custom process to move content management indexes out to the content delivery services. They think this because the content management box detects the indexes needs to be updated and runs the process to update its indexes, but there is nothing on the content delivery boxes to do this. Well this is just not true. To be honest if it was true Sitecore would have a serious short coming if they expected this process to be created manually every time by everyone.

Alex Shyba has written a great post with additional details on how all this works. Of course there is also the Sitecore docs you can reference.

The fact is the web.config file or your own include configs (best approach is in the app_config include folder) have values that can be set to tell the content delivery servers to check at a certain interval to see if their indexes need to be updated. To do this there are a couple key config values you need to set.

<setting name="Indexing.UpdateInterval" value="00:05:00"/>

This setting tells the servers how often to check for index updates. This does not mean the index will always update this often. It only means it will check to see if it needs to update. If you want details on what it is checking and how it knows if the index is dirty please see Alex’s blog.

There is another key setting you have to have as well to make this work on the content delivery servers.

<setting name="Indexing.ServerSpecificProperties" value="true"/>

If this value is not set, or set to false, on the content delivery servers your indexes will never update. Again see Alex’s blog for details on why.

This may or may not light things up for you. There is one more key config file in the web.config you have to enable. If you read Alex’s blog he mentioned the event queues (but never this value). By default Event Queues are disabled in the web.config. If they are disabled this notification about indexes will not make its way to the content delivery servers. 

<setting name="EnableEventQueues" value="true" />

Make sure this setting is also true. Once you have all of these set the content delivery servers should start updating on the defined interval on their on when a index event is queued. Don’t make your UpdateInterval to short as it could start causing performance issues (if it is set to 00:00:00 it is disabled).

Comments

Anonymous said…
You can play games of your alternative and withdraw winnings lengthy as|so long as} you meet the terms and conditions. All your favorite on-line on line casino games and the profitable iRush Rewards dedicated on-line on line casino rewards program makes BetRivers a should for on-line on line casino players. Plus, 빅카지노 the one-time wagering requirement on the deposit match bonus makes it simple to clear. The bonus you choose relies upon entirely on your individual needs as a player. However, there are some deals that lend themselves better to sure teams of users than others.

Popular posts from this blog

Experience Profile Anonymous, Unknown and Known contacts

When you first get started with Sitecore's experience profile the reporting for contacts can cause a little confusion. There are 3 terms that are thrown around, 1) Anonymous 2) Unknown 3) Known. When you read the docs they can bleed into each other a little. First, have a read through the Sitecore tracking documentation to get a feel for what Sitecore is trying to do. There are a couple key things here to first understand: Unless you call " IdentifyAs() " for request the contact is always anonymous.  Tracking of anonymous contacts is off by default.  Even if you call "IdentifyAs()" if you don't set facet values for the contact (like first name and email) the contact will still show up in your experience profile as "unknown" (because it has no facet data to display).  Enabled Anonymous contacts Notice in the picture I have two contacts marked in a red box. Those are my "known" contacts that I called "IdentifyAs"

Excel XIRR and C#

I have spend that last couple days trying to figure out how to run and Excel XIRR function in a C# application. This process has been more painful that I thought it would have been when started. To save others (or myself the pain in the future if I have to do it again) I thought I would right a post about this (as post about XIRR in C# have been hard to come by). Lets start with the easy part first. In order to make this call you need to use the Microsoft.Office.Interop.Excel dll. When you use this dll take note of what version of the dll you are using. If you are using a version less then 12 (at the time of this writing 12 was the highest version) you will not have an XIRR function call. This does not mean you cannot still do XIRR though. As of version 12 (a.k.a Office 2007) the XIRR function is a built in function to Excel. Prior version need an add-in to use this function. Even if you have version 12 of the interop though it does not mean you will be able to use the function. The

Uniting Testing Expression Predicate with Moq

I recently was setting up a repository in a project with an interface on all repositories that took a predicate. As part of this I needed to mock out this call so I could unit test my code. The vast majority of samples out there for mocking an expression predicate just is It.IsAny<> which is not very helpful as it does not test anything other then verify it got a predicate. What if you actually want to test that you got a certain predicate though? It is actually pretty easy to do but not very straight forward. Here is what you do for the It.IsAny<> approach in case someone is looking for that. this .bindingRepository.Setup(c => c.Get(It.IsAny<Expression<Func<UserBinding, bool >>>())) .Returns( new List<UserBinding>() { defaultBinding }.AsQueryable()); This example just says to always return a collection of UserBindings that contain “defaultBinding” (which is an object I setup previously). Here is what it looks like when you want to pass in an exp

Security Config in IIS Express

I have gotten tired of always having to look this up or remember where it is at. That means it is time to post to my blog so I can find it easier and hopefully others can too. If you are having issues with IIS Express authentication errors (like the Unauthorized 401.2 error I always get) here is some help. I can never remember what the last setting was I had IIS Express set to for authorization. To change IIS Express for windows auth or anonymous auth you want to work with the applicationhost.config file. It can be found here …Documents\IISExpress\config. You want to change the settings in the following area of the config file. < authentication > < anonymousAuthentication enabled ="true" userName ="" /> < basicAuthentication enabled ="false" /> < clientCertificateMappingAuthentication enabled ="false" /> < digestAuthentication enabled ="false" />

WPF Localization - RESX Option

About a year ago I was building a WPF project in .Net 3.0 and Visual Studio 2005. I wanted to revisit this subject and see what has changed in .Net 3.5 and Visual Studio 2008. I will make a few of these posts to try and cover all the different options (RESX option, LocBaml option, Resource Dictionary Option). In this blog I will focus on using a resx file to localize an application. To show how the resx option is done I created a WPF form with three labels on it. The first label has is text set inline in XAML, the second has it text set via code behind from the resx file and the third has its text set via XAML accessing the resx file. The first thing that needs to happen to setup a project for localization is a small change to the project file. To make this change you will need to open the project file in notepad (or some other generic editor). In the first PropertyGroup section you need to add the follow XML node <UICulture>en-US</UICulture>. So the project file node w