Moving content to trash causes a remote event storm (all providers)

Found in

EPiServer.CMS.Core 10.0.1

Fixed in

EPiServer.CMS.Core 10.3.1

Created

Dec 28, 2016

Updated

May 23, 2017

Area

CMS Core

State

Closed, Fixed and tested


Description

Steps to reproduce:

  1. Configure event replication in a load balanced environment.
  2. Move a page or document to the trash in edit mode.
  3. Watch the network traffic and cpu load in one of the load balanced servers. Notice CPU spiking to 100 percent.

This applies to all providers, for example using the Azure ServiceBus provider you will notice several millions messages until the service bus runs out of quota. The root cause is that the remote events related to ContentLanguageSettingsHandler ends up in a loop and is continously clearing the language settings cache.