COU-614 - Examine indexes not updated on front end servers

Created by David Peck 25 Aug 2017, 12:08:21 Updated by Chris Van Oort 29 Mar 2018, 20:23:09

EDIT: I've re-written this ticket because my investigations have concluded that there is an issue.

I have four websites (separate instances but similar setup) running on 3 live servers. For all four sites; when we courier from a staging server to the master servers, the examine indexes are updated on the master server but not on the front end servers. If I publish on the master server it updates the examine indexes on the master and front end servers. We don't appear to have any load balancing issues and the master server is definitely correctly identified having inspected the umbracoServers table.

Comments

David Peck 25 Aug 2017, 12:49:36

Actually having read https://our.umbraco.org/documentation/getting-started/setup/server-setup/load-balancing/files-replicated it appears the examine indexes shouldn't be replicated anyway. This would imply there is an issue. Could there be anything about my setup which is causing this, rather than it being a global issue?


David Peck 25 Aug 2017, 15:14:33

Someone else with the issue: https://our.umbraco.org/forum/umbraco-pro/courier/27641-Load-Balanced-Environments


David Peck 29 Aug 2017, 11:37:09

Log from slave server just reads:

 2017-08-29 12:35:41,495 [P9224/D7/T39] DEBUG Umbraco.Web.Scheduling.ScheduledPublishing - Does not run on slave servers.
 2017-08-29 12:35:41,495 [P9224/D7/T32] DEBUG Umbraco.Web.Scheduling.ScheduledTasks - Does not run on slave servers.
 2017-08-29 12:35:41,495 [P9224/D7/T32] DEBUG Umbraco.Web.Scheduling.BackgroundTaskRunner - [ScheduledTasks] Task added Umbraco.Web.Scheduling.ScheduledTasks
 2017-08-29 12:35:41,495 [P9224/D7/T39] DEBUG Umbraco.Web.Scheduling.BackgroundTaskRunner - [ScheduledPublishing] Task added Umbraco.Web.Scheduling.ScheduledPublishing


David Peck 31 Aug 2017, 08:09:12

I've created a hacky workaround if anyone else has this problem. https://gist.github.com/drpeck/fbaf6f8f3acb58b834dc8947aae1083e

Essentially it just uses examine events (because Courier's extraction events don't work) to republish the page on the master server shortly after the original publish. This causes two publishes always, but in my environment that isn't a big deal.


Nathan Skidmore 24 Jan 2018, 10:39:19

I am experiencing the same issue in a flexible load balanced environment. We need to manually publish the couriered item at the destination 'master' server for the indexes to update on our front-end web servers.


Chris Van Oort 29 Mar 2018, 20:23:09

I'm experiencing the same issue on a non-load balanced site: https://our.umbraco.org/forum/umbraco-courier/91363-courier-transfers-everything-but-doesnt-republish-pages-on-the-destination-site

Same experience as @Nathan where I have to manually publish content items on production.


Priority: Normal

Type: Bug

State: Submitted

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 3.1.2, 3.1.3

Due in version:

Sprint:

Story Points:

Cycle: