Sitecore 8.1 caching issue in cluster enviroment

Question

We have hosted Sitecore 8.1 website on two server node1 and node2 where request redirection is handled by Load balancer. While deployment we delete App_config, Assets and Areas folder and copy-paste/replace all files so assuming we have same code on both server.

Still we are facing caching issue on node1 even configuration is same. While publishing every time we have to clear cache on node1 ( /sitecore/admin/cache.aspx ) because published content is not displayed on node1. Don't have any issue on node2.

-----------------UPDATE 02/13------------------------

We have following patch files on both node

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
  <sitecore>
    <events timingLevel="custom">
      <event name="publish:end">
        <handler type="Sitecore.Publishing.HtmlCacheClearer, Sitecore.Kernel" method="ClearCache">
          <sites hint="list">
            <patch:delete />
          </sites>
          <sites hint="list">
            <site>website1</site>
            <site>website2</site>
           </sites>
        </handler>
      </event>
      <event name="publish:end:remote">
        <handler type="Sitecore.Publishing.HtmlCacheClearer, Sitecore.Kernel" method="ClearCache">
          <sites hint="list">
            <patch:delete />
          </sites>
          <sites hint="list">
            <site>website1</site>
            <site>website2</site>
          </sites>
        </handler>
      </event>
    </events>
  </sitecore>
</configuration>

Answer 1

Go to the sitecore/admin/showconfig.aspx and check if you have the following entry in there:

<event name="publish:end:remote">
    <handler type="Sitecore.Publishing.HtmlCacheClearer, Sitecore.Kernel" method="ClearCache">
        <sites hint="list">
            <site>website</site>
            <site>website2</site>
        </sites>
    </handler>
</event>

If you don't have this entry in place, this means that you have to configure your automated cache clearing.

Please, follow the steps from this community guide on how to set up the automated cache clearing correctly: https://community.sitecore.net/technical_blogs/b/sitecorejohn_blog/posts/clear-output-caches-for-all-managed-sites-after-publication-with-the-sitecore-asp-net-cms

Answer 2

Scalability Setting Issues are Common Cause for Event Misfires on Content Delivery Servers

On Content Delivery servers, especially when more than one are in play, it is a requirement, that the InstanceName Sitecore Setting is unique for each Content Delivery Server.

Sitecore uses the instance name to determine whether or not a server needs to act on any given events that are collected. In the event that both Content Delivery servers are being given the same InstanceName, when one server receives the event, it writes it's instance back to the EventQueue table in the Core database. If the second server, of same Instance Name, attempts to check EventQueue for work, it'll see that it already processed that event, and thus will not act on it.

To Resolve

1. Make sure the ScalabilitySettings.config is enabled.
2. Ensure One of the Following is True
   • Ensure that the InstanceName Sitecore Setting found in App_Config/Include/ScalabilitySettings.config is unique and different on both Content Delivery Servers.
   • If InstanceName is left blank, it will utilize MACHINENAME\IISSITENAME or the Azure App Service resolved name for the instance.