Why do you want to "realize a distributed caching layer based on disk-speed and
storage?”
Providing that you are running nginx on a healthy host running linux then your
HDD-cache
be faster (or the seem speed) as your SSD-cache. This because the cached file
will be
written though the Linux p
Hi,
Thank you Maxim and Reinis for your replies. I verified that when the
response from backend-hdd-cache gets cached in the front-end ssd-cache, the
response includes the X-Upstream-Server-Cache-Status header added from the
hdd-cache-upstream.Hence, I am seeing two headers in a response served by
> Why am I getting the header twice for the 6th request. In this case, the
> request is HIT by the SSD cache itself, and there is no request sent to local
> upstream also.
>
> So, shouldn't I be getting only one instance of the header in the response?
Nginx saves the object with all the headers f
Hello!
On Fri, Oct 06, 2017 at 03:05:52AM -0400, rnmx18 wrote:
[...]
> For the 6th request, I see the following:
>
> < X-UpStream-Server-Cache-Status: HIT
> < X-UpStream-Server-Cache-Status: HIT
>
> Why am I getting the header twice for the 6th request. In this case, the
> request is HIT by th
Hi,
To realize a distributed caching layer based of disk-speed and storage, I
have prepared the following configuration with an SSD-cache and HDD-cache.
http {
add_header X-UpStream-Server-Cache-Status $upstream_cache_status;
# proxy caching configurations
proxy_cache_path /tmp/myss
