[
https://issues.apache.org/jira/browse/CASSANDRA-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stu Hood updated CASSANDRA-1434:
--------------------------------
Attachment: 0001-Switch-to-TFramedTransport-in-TestRingCache.patch
0002-Add-kth-endpoint-method-to-RingCache-and-improve-con.patch
0003-Remove-nesting-in-RingCache.patch
0001 and 0003 are minor fixes, but 0002:
* Avoids blocking processing for writes (but only 2 * batchSize mutations may
be in memory at a time, so we may still block)
* Changes the default batchSize to 2^14
* Rotates through possible endpoints for a range per flush, which should more
evenly distribute client connections when there are small numbers of keys in
play
One issue we haven't tackled yet is how to handle failures: I've reopened
CASSANDRA-1264 to handle that.
> ColumnFamilyOutputFormat performs blocking writes for large batches
> -------------------------------------------------------------------
>
> Key: CASSANDRA-1434
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1434
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Reporter: Stu Hood
> Fix For: 0.7.0
>
> Attachments: 0001-Switch-to-TFramedTransport-in-TestRingCache.patch,
> 0002-Add-kth-endpoint-method-to-RingCache-and-improve-con.patch,
> 0003-Remove-nesting-in-RingCache.patch
>
>
> By default, ColumnFamilyOutputFormat batches
> {{mapreduce.output.columnfamilyoutputformat.batch.threshold}} or
> {{Long.MAX_VALUE}} mutations, and then performs a blocking write.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
