On Mon, Mar 14, 2011 at 1:03 PM, Daniel Doubleday
wrote:
> I was thinking of setting the work queue in CFS.flushWriterPool to
>
> new LinkedBlockingQueue(3) // because 3 is my favorite number
>
> instead of
>
> new
> LinkedBlockingQueue(DatabaseDescriptor.getAllDataFileLocations().length)
>
Alter
Sure, that should be fine.
On Mon, Mar 14, 2011 at 1:03 PM, Daniel Doubleday
wrote:
> Hi all,
>
> on 0.6:
>
> we are facing increased write latencies every now and then when an
> unfortunate write command thread becomes the flush writer for a mem table
> because of an already running mem table
Hi all,
on 0.6:
we are facing increased write latencies every now and then when an unfortunate
write command thread becomes the flush writer for a mem table because of an
already running mem table flush.
I was thinking of setting the work queue in CFS.flushWriterPool to
new LinkedBlockingQu
