[jira] [Commented] (CASSANDRA-6764) Using Batch commitlog_sync is slow and doesn't actually batch writes

["John Carrino (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911145#comment-13911145 ] 

John Carrino commented on CASSANDRA-6764:
-----------------------------------------

I tried to stick as close as I could to the coding guidelines so let me know if I missed some stuff.  (my native java style is open curly on the end of the line).

Also let me know if there are any other config params I should add.

> Using Batch commitlog_sync is slow and doesn't actually batch writes
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-6764
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6764
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: John Carrino
>             Fix For: 1.2.16
>
>         Attachments: cassandra_6764_v2.patch
>
>
> The assumption behind batch commit mode is that the client does it's own batching and wants to wait until the write is durable before returning.  The problem is that the queue that cassandra uses under the covers only allows for a single ROW (RowMutation) per thread (concurrent_writes).  This means that commitlog_sync_batch_window_in_ms should really be called sleep_between each_concurrent_writes_rows_in_ms.
> I assume the reason this slipped by for so long is that no one uses batch mode, probably because people say "it's slow".  We need durability so this isn't an option.
> However it doesn't need to be this slow.
> Also, if you write a row that is larger than the commit log size it silently (warn) fails to put it in the commit log.  This is not ideal for batch mode.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)