Re: page allocation failures on osd nodes

2013-01-26 Thread Andrey Korolyov
On Sat, Jan 26, 2013 at 3:40 AM, Sam Lang sam.l...@inktank.com wrote: On Fri, Jan 25, 2013 at 10:07 AM, Andrey Korolyov and...@xdel.ru wrote: Sorry, I have written too less yesterday because of being sleepy. That`s obviously a cache pressure since dropping caches resulted in disappearance of

Re: RadosGW performance and disk space usage

2013-01-26 Thread Cesar Mello
Dear Sam, Dan and Marcus, Thank you a lot for the replies. I'll do more tests today. The length of each object used in my test is just 20 bytes. I'm glad you got 400 objects/s! Iif I get that with a length of 8 KB using a 2-node cluster, then ceph with rados will be already faster than my

[PATCH 0/4] rbd: keep reference to lingering object requests

2013-01-26 Thread Alex Elder
This series applies on top of the new rbd request code. When an osd request is marked to linger the osd client will keep a copy of the request, and will resubmit it if necessary. If it gets resubmitted, it will also call the completion routine again, and because of that we need to make sure the

[PATCH 1/4] rbd: unregister linger in watch sync routine

2013-01-26 Thread Alex Elder
Move the code that unregisters an rbd device's lingering header object watch request into rbd_dev_header_watch_sync(), so it occurs in the same function that originally sets up that request. Signed-off-by: Alex Elder el...@inktank.com --- drivers/block/rbd.c | 10 -- 1 file changed, 4

[PATCH 4/4] rbd: don't drop watch requests on completion

2013-01-26 Thread Alex Elder
The new request code arranges to get a callback for every osd request we submit (this was not the case previously). We register a lingering object watch request for the header object for each mapped rbd image. If a connection problem occurs, the osd client will re-submit lingering requests. And