[
https://issues.apache.org/jira/browse/CASSANDRA-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913654#action_12913654
]
Stu Hood commented on CASSANDRA-1434:
-------------------------------------
* There is a race condition in put() between {{!run}} and the put itself
* Exceptions thrown by child threads will be logged, but not reported to the
Hadoop frontend, since they aren't what kill the parent thread
I'm -0 on v3 and v4: but I'll add a 0005 to separate queue size from batch
size, so that we can tune down the batch size for Flip.
> 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
> Assignee: Stu Hood
> Fix For: 0.7 beta 2
>
> Attachments:
> 0001-Switch-away-from-Multimap-and-fix-regression-introdu.patch,
> 0002-Improve-concurrency-and-add-basic-retries-by-attempt.patch,
> 0003-Switch-RingCache-back-to-multimap.patch,
> 0004-Replace-Executor-with-map-of-threads.patch, 1434-v3.txt, 1434-v4.txt
>
>
> 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.
