[
https://issues.apache.org/jira/browse/CASSANDRA-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1434:
--------------------------------------
Attachment: 1434-v6.txt
v6.
bq. There is a race condition in put() between !run and the put itself
not really. the check in put is just an attempt to abort earlier if possible.
bq. Exceptions thrown by child threads will be logged, but not reported to the
Hadoop frontend
saved actual exceptions.
bq. the second open in RangeClient is getting TTransportException: Socket
already connected
fixed
bq. Logging a NPE for the first batch is pretty ugly
nothing is logged. the alternatives strike me as uglier.
bq. The default batchSize was increased back up to Long.MAX_VALUE
fixed
> 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: Jonathan Ellis
> 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,
> 1434-v5.txt, 1434-v6.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.
