cuttlefish punch list

cuttlefish punch list

[Sage Weil]

There are two big items I'm concerned about:

#4815, and the other large monitor store problems with syncing and failure 
to get quorum.  We need to confirm
 - why the sync is failing and we're hitting that assert, and
 - why the store.db's are growing so huge

#4853: This is triggered by one of the upgrade tests and looks like it 
could be a regression from the client request replay fix last week.

A few other things:

 - the rgw upgrade tests are failing because the s3tests, readwrite, and 
   swift tasks can't be rung twice in a row.
 - ceph release build needs to include raring.
 - ceph-deploy build needs to include raring too.

Thanks!
sage

Re: cuttlefish punch list

[Sage Weil]

On Mon, 29 Apr 2013, Sage Weil wrote:
> There are two big items I'm concerned about:
> 
> #4815, and the other large monitor store problems with syncing and failure 
> to get quorum.  We need to confirm
>  - why the sync is failing and we're hitting that assert, and
>  - why the store.db's are growing so huge

This appears to be a bad interaction between the mon workload and levedb's 
compaction heuristics.  We've worked around it in wip-mon-compact; anyone 
who has seen large mon stores and/or a failure to sync, please try this 
branch!

> #4853: This is triggered by one of the upgrade tests and looks like it 
> could be a regression from the client request replay fix last week.

Fixed.

> A few other things:
> 
>  - the rgw upgrade tests are failing because the s3tests, readwrite, and 
>    swift tasks can't be rung twice in a row.

Running now.

>  - ceph release build needs to include raring.
>  - ceph-deploy build needs to include raring too.

Tomorrow.

Thanks everyone!  We're close!
sage

kernel 3.9 / new networking options for RADOS

[Kasper Dieter]

What are the options for RADOS to make use of the new
networking feature in Kernel 3.9 ?

http://www.h-online.com/open/features/What-s-new-in-Linux-3-9-1845705.html

TCP and UDP sockets now support a SO_REUSEPORT option that allows multiple
sockets to listen on the same port. This enables, for example, multiple
web server processes or threads to open individual sockets to listen
on port 80; any connections that come in on this port will be evenly
distributed across the sockets by the kernel.

This approach aims to improve the way workloads are distributed across the
available processor cores. (...) this extension can help avoid bottlenecks
that appear in certain situations when only one thread accepts new
connections and then distributes them across other threads. (...)


Kind Regards,
-Dieter