Splunk® Enterprise

Upgrade Readiness

Clear the cache in the Upgrade Readiness App

If you find inconsistencies in your scans between your Splunk platform nodes, between two or more users, or between the scan results in your weekly emails, then clearing the Upgrade Readiness App (URA) cache might resolve these inconsistencies.

The uraclearcache SPL command clears all URA scan results and cache data on all nodes within an indexer cluster. This includes all nodes with access to the same KV store instance as the node on which you run the command.

This command is available in the Upgrade Readiness App versions 4.6.x and higher.

Data loss when clearing the cache

The uraclearcache command deletes all URA data, including scan results, caches, reports, and summaries. This includes URA data generated by automated and manual scan results for all users.

Do not use this command unless you want to permanently delete the following data.

This command deletes the following files from the python_upgrade_readiness_app/local/ directory:

  • jquery_sha512_hash.json
  • sha512_hash.json
  • emerald_sha512_hash.json

This command also deletes the entire contents of all the following directories within the python_upgrade_readiness_app/local/ directory:

  • /jquery_merged
  • /jquery_reports
  • /jquery_remote
  • /jquery_scan_summary
  • /emerald_merged
  • /emerald_reports
  • /emerald_remote
  • /emerald_scan_summary
  • /merged
  • /reports
  • /remote
  • /scan_summary

Clear the cache

Complete the following steps to clear the cache in the URA.

  1. Choose a time when you can afford higher than normal resource utilization.

    During ordinary scanning, the URA returns results quickly by using cached results from previous scan operations. When you use the uraclearcache command, however, the URA runs all scan operations on every stack node, which can cause above-average resource utilization. Resource utilization returns to normal after the new results are cached.

  2. Log in as a user with admin or sc_admin roles, or a user with the admin_all_objects permission.
  3. Access the URA search context at the following URL: https://<user-specified domain>.splunkcloud.com/en-US/app/python_upgrade_readiness_app/search.
  4. Run the | uraclearcache command in the Search bar within the URA.

After clearing the cache, wait until the next automated scan completes before you run any manual scans. It takes up to 24 hours for the URA to remove the result and cache data, and up to an additional 24 hours to generate new scan data.

Last modified on 05 November, 2024
 

This documentation applies to the following versions of Splunk® Enterprise: 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters