The Problem Recently, I was checking my CD server logs for an issue that was reported and stumbled across some log entries which mentioned about index update jobs getting triggered as in snapshot below- This made me think that should these jobs actually get triggered from CDs?? The answer is NO! Why?? Because web indexes already get updated from CM servers during item publish events etc. (if the indexes are already maintained by the CM instance). Doing the same from CD servers is redundant and increasing unwanted load of index update jobs on CD servers. Also, CD servers are only supposed to READ from indexes and not WRITE to them (in most cases) Then why are these jobs getting created? I started looking into my index configurations on CD servers and from what I could see, all the web indexes in our case on the CD instances are configured with "onPublishEndAsync", "remoteRebuild" or "rebuildAfterFullPublish" strategies. As per Sitecore best practice, if
This blog is created to serve as a repository of quick tips for Sitecore developers. I have learnt a lot from the programming community and this is my attempt to give back to the community.