atom feed38 messages in ru.sysoev.nginxRe: mogilefs module 1.0.2
FromSent OnAttachments
Valery KholodkovJul 25, 2009 10:21 am 
Michael ShadleJul 25, 2009 12:56 pm 
Valery KholodkovJul 25, 2009 2:20 pm 
Michael ShadleJul 25, 2009 2:43 pm 
Igor SysoevJul 27, 2009 2:47 am 
Valery KholodkovJul 27, 2009 2:48 am 
Michael ShadleJul 27, 2009 8:57 am 
Michael ShadleJul 27, 2009 8:59 am 
Valery KholodkovJul 27, 2009 10:47 am 
DanielJul 27, 2009 9:09 pm 
Valery KholodkovJul 27, 2009 10:51 pm 
Michael ShadleJul 27, 2009 11:03 pm 
Michael ShadleJul 27, 2009 11:07 pm 
Valery KholodkovJul 27, 2009 11:14 pm 
Valery KholodkovJul 27, 2009 11:21 pm 
Michael ShadleJul 28, 2009 12:38 am 
Michael ShadleJul 28, 2009 12:41 am 
Valery KholodkovJul 28, 2009 3:45 am 
Valery KholodkovJul 28, 2009 3:54 am 
Michael ShadleJul 28, 2009 10:14 am 
Michael ShadleJul 28, 2009 10:16 am 
Valery KholodkovJul 30, 2009 3:27 am 
Valery KholodkovJul 30, 2009 4:35 am 
Michael ShadleJul 30, 2009 9:47 am 
Michael ShadleJul 30, 2009 9:51 am 
DanielAug 6, 2009 8:33 pm 
Valery KholodkovAug 7, 2009 3:58 am 
Valery KholodkovAug 7, 2009 10:15 am.patch
DanielAug 10, 2009 1:54 am 
Valery KholodkovAug 10, 2009 11:14 am.patch
DanielAug 10, 2009 10:08 pm 
gogobuAug 30, 2009 12:46 am 
Valery KholodkovAug 30, 2009 1:56 am 
gogobuAug 30, 2009 5:44 am 
Valery KholodkovAug 30, 2009 6:41 am 
gogobuAug 30, 2009 8:15 am 
Michael ShadleAug 30, 2009 11:32 am 
daventAug 31, 2009 8:56 am 
Subject:Re: mogilefs module 1.0.2
From:gogobu (ngin@nginx.us)
Date:Aug 30, 2009 8:15:24 am
List:ru.sysoev.nginx

Valery Kholodkov Wrote:

-------------------------------------------------------

gogobu wrote:

I've noticed the following config settings in the document:

proxy_hide_header Content-Type;

This you need in case if storage node does not specify correct content type (and it usually does not). The content type will be then resolved via request URI extension.

proxy_buffering off;

This prevents nginx from accumulating response in memory or writing ont disk, thus saving resources which were already used on storage node.

Is there any particular reason for this setting?

Just an idea, is it possible to enable

proxy_buffering and use proxy_cache to cache the tracker URLs?

It is possible to enable proxy_buffering and I don't know what impact on performance it will have. And it is not possible to cache the URLs returned by the tracker, but might be possible to cache the returned entity itself.

Got it. Thanks for the explanation.

Caching the entity itself is probably too heavy... it would be better if you
could implement the cache feature for the URLs so the trackers would be less
stressed.

Thanks and please keep up the good work! Michael

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,4462,5349#msg-5349