logo

NJP

Steps to determine the cause of a cache flush

Import · Apr 08, 2020 · article

This article walks you through the process to determine the cause of the cache flush.

Below are a few causes that will lead to the cache to be rebuilt:

1) Adding or updating system properties

2) Adding or updating dictionary entries

3) Committing update sets

4) Adding or updating translations

5) Activating a plugin

6) User triggered cache flush by accessing /cache.do

Resolution

Below are the different ways to determine if a cache flush was triggered that lead to poor performance of the instance.

1) ServiceNow Performance Dashboard:

The ServiceNow Performance graphs will provide data upto 30 days and you have an option to view if any event was triggered within that time frame based on each of the nodes available.

There is an option to toggle the Diagnostic Events to on and off. Enabling this will provide you all the events that were triggered as follows. In the below picture, there was a plugin that was activated that lead to the cache flush and you can see the spikes in response time once the cache was flushed.

image

Below is the link to the documentation:

https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/platform-performa...

There are diagnostic events that are triggered by the platform when there are certain changes noticed in the instance. There will be entries made in 'diagnostic_event' table and in the log files. Data in the 'diagnostic_event' table is maintained for about 720 hours or 30 days.

When the cache is flushed, the entry in 'diagnostic_event' table will have name = cache.flush with detail ='Flushing entire system cache' is inserted.

Below is the snippet from the logs:

2019-07-24 09:14:00 (024) worker.0 worker.0 txid=28c8391edbb6 WARNING *** WARNING *** Starting cache flush

2019-07-24 09:14:00 (025) worker.0 worker.0 txid=28c8391edbb6 [DiagnosticEvent] c2c8b91edbb67340ac639ee5db96190dcache.flushFlushing entire system cacheWarningInformation2019-07-24 16:14:00app129019.sjc103.service-now.com:testinstance0032019-07-24 09:14:00 (031) worker.0 worker.0 txid=28c8391edbb6 Flushing cache2019-07-24 09:14:01 (244) worker.0 worker.0 txid=28c8391edbb6 Loading properties from DB2019-07-24 09:14:01 (331) worker.0 worker.0 txid=28c8391edbb6 WARNING *** WARNING *** Cache flush complete2019-07-24 09:14:01 (332) worker.0 worker.0 txid=28c8391edbb6 Loading properties from DB2019-07-24 09:14:01 (409) worker.0 worker.0 txid=28c8391edbb6 GlideSession SuppressTextIndexWhenSessionWorkflowOff is set to previous value true for plugin x_70091_first_sugg

2019-07-24 09:14:01 (490) worker.0 worker.0 txid=28c8391edbb6 [DiagnosticEvent] 5ec8b91edbb67340ac639ee5db961910plugin.activationPlugin ID: First Suggestion BoxInformationClosed2019-07-24 16:14:01app129019.sjc103.service-now.com:testinstance003

View original source

https://www.servicenow.com/community/in-other-news/steps-to-determine-the-cause-of-a-cache-flush/ba-p/2268567