Hi...we ran into problem when attempted to use Cache Inspector for Regex
Lookup & Delete cached objects from an ATS cache VM (single object lookup
and deletion was OK).
Following is our set up details:
Current Version: 4.2.1
“Pristine is enabled”
Cache Objects Present: ~150K
Cached bytes used: ~50GB
Sample CI regexp lookup/deletion command when kicked off from “curl” (we
have titles title_001 to title_250 to mimic 250 x VOD titles with ~600
objects per title):
- curl
http://<app_id>/ci/lookup_regex?url=http://<sample_origin_domain>/title_199/*
- curl
http://<app_id>/ci/delete_regex?url=http://<sample_origin_domain>/title_199/*
Two problems
1.) The regex request resulted in CI reporting “Network Error” after ~10min
(with access log reporting cache result code of “ERR_CLIENT_ABORT”). Is
this a known issue for this many of (~150K) cache objects?
Our target Production VM is to host over 10M+ cache objects per VM
and the observed regex lookup/deletion performance did not look OK to
support Operations needs (if we are to lookup/purge objects by pattern)
2.) We also noticed when the regex lookup failed/aborted on client side,
the regex request continued to run at the ATS with cache disk(s) at ~100%
utilization. The request then stopped when
“proxy.config.http.transaction_active_timeout_in”
(default: 900 sec) kicked in. When we increased the timeout to 2HR,
the above request alone by itself took over 1HR (~1.3HR to be exact) to
complete on a quiet VM (no traffic load). When we repeated the same test
with 500 titles
provisioned (~300K cache objects). The similar regex request took
over 2HRs (and aborted at 2HR mark when
proxy.config.http.transaction_active_timeout_in kicked in) which was not
good.
Is there any work-around so we can reliably lookup and purge
multiple objects sharing certain pattern?
