cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1434) ColumnFamilyOutputFormat performs blocking writes for large batches
Date Mon, 27 Sep 2010 20:44:36 GMT


Jonathan Ellis updated CASSANDRA-1434:

    Attachment: 1434-v6.txt


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


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


> ColumnFamilyOutputFormat performs blocking writes for large batches
> -------------------------------------------------------------------
>                 Key: CASSANDRA-1434
>                 URL:
>             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.

View raw message