rwise redundant down-stream requests prior to the file being cached.)
On Jul 1, 2014, at 4:11 PM, Paul Schlie wrote:
> Thank you for your patience.
>
> I mistakenly thought the 5 second default value associated with
> proxy_cache_lock_timeout was the maximum delay allowed between succes
activity of the stream; as in most circumstances,
redundant streams should never be opened, as it will tend to only make matters
worse.
Thank you.
On Jul 1, 2014, at 12:40 PM, Maxim Dounin wrote:
> On Tue, Jul 01, 2014 at 10:15:47AM -0400, Paul Schlie wrote:
>> Then how could multiple st
20 AM, Maxim Dounin wrote:
> Hello!
>
> On Tue, Jul 01, 2014 at 08:44:47AM -0400, Paul Schlie wrote:
>
>> As it appears a downstream response is not cached until first
>> completely read into a temp_file (which for a large file may
>> require 100's if not 1,000&
nd a backend server may be formed, each
most likely transferring the same information needlessly; being what
proxy_cache_lock was seemingly introduced to prevent (but it doesn't)?
On Jul 1, 2014, at 7:01 AM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Jun 30, 2014 at 11:10:52P
ed.
On Jun 30, 2014, at 9:32 PM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Jun 30, 2014 at 09:14:06PM -0400, Paul Schlie wrote:
>
>> (Seemingly, it may be beneficial to simply replace the
>> sequentially numbered temp_file scheme with hash-named scheme,
>> wher
respectively
logically accessed as a local static file, or deleted upon no longer being
needed and not being cached; and thereby kill multiple birds with one stone
per-se?)
On Jun 30, 2014, at 8:44 PM, Paul Schlie wrote:
> Is there any possible solution for this problem?
>
> As
oxy'd reads,
regardless of whether they're using a cache hashed naming scheme for
proxy_cache files, or a symbolic naming scheme for reverse proxy'd static
files; it would be nice if the fix were applicable to both.)
On Jun 24, 2014, at 10:58 PM, Paul Schlie wrote:
> Hi, U
I don't know if what you're experiencing is related to a problem I'm still
tracking down, specifically that multiple redundant read-streams and
corresponding temp_files are being opened to read the same file from a backend
server for what appears to be a single initial get request by a client fo
Hi, Upon further testing, it appears the problem exists even with proxy_cache'd
files with "proxy_cache_lock on".
(Please consider this a serious bug, which I'm surprised hasn't been detected
before; verified on recently released 1.7.2)
On Jun 24, 2014, at 8:58 PM, Pau
Again thank you. However ... (below)
On Jun 24, 2014, at 8:30 PM, Maxim Dounin wrote:
> Hello!
>
> On Tue, Jun 24, 2014 at 07:51:04PM -0400, Paul Schlie wrote:
>
>> Thank you; however it appears to have no effect on reverse proxy_store'd
>> static files?
>
Jun 24, 2014 at 02:49:57PM -0400, Paul Schlie wrote:
>
>> I've noticed that multiple (as great as 8 or more) parallel
>> redundant streams and corresponding temp_files are opened
>> reading the same file from a reverse proxy backend into nginx,
>> upon e
I've noticed that multiple (as great as 8 or more) parallel redundant streams
and corresponding temp_files are opened reading the same file from a reverse
proxy backend into nginx, upon even a single request by an up-stream client, if
not already cached (or stored in a static proxy'ed file) loca
12 matches
Mail list logo
