SAP Knowledge Base Article - Preview

2969041 - CCv2 - Web Cache on storefront endpoints

Symptom





Web Cache on storefront endpoints is implemented as Apache mod_proxy with:

  • allocated 5Gi disk space,
  • HTCACHECLEAN_SIZE set to 4Gi
  • HTCACHECLEAN_DAEMON_INTERVAL set to 120 minutes.

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

  • in kubernetes cluster Apache pod could be Evicted (so new one will be created) because:
    - no space for cache when you will cache too many medias in short period of time
    - 120 IOPS limit reached on 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)



Read more...

Environment






Keywords






  • CCv2
  • Web Cache
  • proxy_mod
  • media cache
  • apache evicted
  • CDN
, KBA , CEC-HCS-CCAZ-WEB , Web Layer - Apache , CEC-HCS-CCAZ-OPS , OPS component for General environment management , Known Error

About this page

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

Search for additional results

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