[
https://issues.apache.org/jira/browse/CASSANDRA-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912272#action_12912272
]
Stu Hood commented on CASSANDRA-1434:
-------------------------------------
> it's while (run || isEmpty). am i missing something?
Ah, sorry.
> the idea is it tries each endpoint, then throws if they all fail. (if
> !iter.hasnext() then throw)
Gotcha. I missed that part because there doesn't appear to be a way for the
parent thread to figure out that a client died, so I assumed that the clients
never died. Does it need an UncaughtExceptionHandler that alerts the parent
thread? This was what was accomplished by using offer() rather than put() in
the previous version.
> as described above, batching > 1 is a misfeature that has been demonstrated
> to cause badness in practice.
In Cassandra, or in general?
> 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
>
>
> 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.
