Ok so it seems I might be able to reindex a single node by converting the IContent using the PackagingService. However I cannot find any documentation on that service nor clarity on what the type parameter is.

The below is untested. Is this the correct way to do it?

ExamineManager.Instance
              .IndexProviderCollection[SearchConstants.IndexerName]
              .ReIndexNode(entity.ToXml(packagingService), entity.ContentType.Alias);

I pass the package service as follows...

IPackagingService packagingService = applicationContext.Services.PackagingService;
PageCacheRefresher.CacheUpdated += (sender, e) => this.PageCacheRefresherCacheUpdated(sender, e, packagingService);

James,

Publishing on master should cause publishing on slaves and triggering of all related events including indexing so in theory should not need to do this manually? Unless it does not work?

With regards to reindex Matt had to reindex node recently and got the node xml from cache thereby saving db hit. He is digging out some code

I think my scenario was slightly different, as I have a parent / child document setup where when the child node indexes itself, it grabs content from the parent node to index along with it. So what follows is how I force the childnodes to reindex when the parent node gets updated in the cache. Not sure how much it will help, but it might:

CacheRefresherBase<PageCacheRefresher>.CacheUpdated += (sender, args) =>
    {
        IPublishedContent publishedContent = null;

        if (args.MessageType == MessageType.RefreshById)
        {
            publishedContent = UmbracoContext.Current.ContentCache.GetById((int)args.MessageObject);
        }
        else if (args.MessageType == MessageType.RefreshByInstance)
        {
            publishedContent = UmbracoContext.Current.ContentCache.GetById(((IContent)args.MessageObject).Id);
        }

        if (publishedContent != null && publishedContent.DocumentTypeAlias == Constants.DocTypeAliases.MyDocTypeAlias)
        {
            // Reindex child nodes
            foreach (var child in publishedContent.Children)
            {
                var xmlStr = umbraco.library.GetXmlNodeById(child.Id.ToString()).Current.OuterXml;
                var xml = XElement.Parse(xmlStr);

                ExamineManager.Instance.IndexProviderCollection["ExternalIndexer"]
                    .ReIndexNode(xml, IndexTypes.Content);
            }
        }
    };

Thanks Matt.

This is really helpful as I have the same scenario as you and was stuck as to how to get the child nodes to refresh in the index.

Ver

Hi James,

We are experiencing similar issues. I think you are also using the new flexible loadbalancing introduced in 7.3.

How this works is that when you make a change to a content or a media item a cacheinstruction is written to the database (table umbracoCacheInstruction).

On the first request to your slave app it will look in a file in the folder App_Data/TEMP/DistCache/{machineName}/*-lastsynced.txt. This file contains id of the last cache instruction that has run on your slave server. It will then load all cache instructions from the db with a later id then in the file.

So if you change something on master these changes aren't immediatly executed on the slave instances. They should receive a request first.

As Examine indexes are updated async, so it's possible that request to your page is executed before the index is updated and hence giving you out of date content.

And as I see you are also using outputcache your page will be cached and will not reflect the changes until the next time the cache is refreshed.

We started noticing this when editors were starting to change the focal point on images. The change was immediatly visible on the master server but not on the slaves. To make it visible on the slave servers we need another content change action in the backend (for clearing output cache).

Still looking for a way on how to solve this.

Dave

is working on a reply...