Thank you; however it appears to have no effect on reverse proxy_store'd static files?

(Which seems odd, if it actually works for cached files; as both are first read into temp_files, being the root of the problem.)

Any idea on how to prevent multiple redundant streams and corresponding temp_files being created when reading/updating a reverse proxy'd static file from the backend?

(Out of curiosity, why would anyone ever want many multiple redundant streams/temp_files ever opened by default?)

On Jun 24, 2014, at 6:36 PM, Maxim Dounin <mdounin@mdounin.ru> wrote:

> Hello!
>
> On Tue, 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 even a single request by an up-stream client, if not
>> already cached (or stored in a static proxy'ed file) local to
>> nginx.
>>
>> This seems extremely wasteful of bandwidth between nginx and
>> corresponding reverse proxy backends; does anyone know why this
>> is occurring and how to limit this behavior?
>
> http://nginx.org/r/proxy_cache_lock
>
> --
> Maxim Dounin
> http://nginx.org/
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx