SAP Knowledge Base Article - Preview

2969041 - Commerce Cloud - Web Cache on storefront endpoints



Web Cache on storefront endpoints is implemented with Apache mod_cache and mod_cache_disk with:

  • Allocated 5Gi disk space,
  • HTCACHECLEAN_DAEMON_INTERVAL set to 120 minutes.

Generally, this cache will work well when you will use it with a limited volume of medias, but when you will enable it for many endpoints and many URLs per endpoint, pointing to many medias, it's possible that:

  • In the kubernetes cluster, the Apache pod could be Evicted (and a new one will be created) because:
    - There is no space for cache when you will cache too many medias in short period of time
    - The 120 IOPS limit is reached on the Azure side during cleaning of old medias from cache disk, you can check this in Dynatrace on VM level under storage section
  • Other pods like storefront, backgroundprocessing, backoffice, api, etc which will be located on same VM as Apache could be Evicted too and restarted what could destabilise your environment especially during surge events (in that case you will see again IOPS limit reached on VM level in Dynatrace)





SAP Commerce Cloud all versions


  • CCv2
  • Web Cache
  • mod_proxy
  • mod_cache
  • mode_cache_disk
  • media cache
  • apache evicted
  • CDN
, KBA , CEC-SCC-CLA-ENV-NWC , Network Connectivity , Known Error

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.