[
https://issues.apache.org/jira/browse/CASSANDRA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757898#action_12757898
]
Jonathan Ellis commented on CASSANDRA-401:
------------------------------------------
05
split flusher executor into flushSorter and flushWriter.
This is because sorting is CPU-bound, and writing is disk-bound; we want to
be able to do both at
04
clean up ThreadFactoryImpl and rename to NamedThreadFactory
03
r/m unused commitlogcontext arg to flush. synchronize getTempSSTablePath
> Less crappy failure mode when swamped with inserts than "run out of memory
> and gc-storm to death"
> -------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-401
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.5
>
> Attachments: 0001-CASSANDRA-401.txt, 0001-CASSANDRA-401.txt,
> 0002-clean-out-unused-code-from-MessagingService.-Inline-si.txt,
> 0002-clean-out-unused-code-from-MessagingService.-Inline-si.txt,
> 0003-r-m-unused-commitlogcontext-arg-to-flush.-synchronize.txt,
> 0004-clean-up-ThreadFactoryImpl-and-rename-to-NamedThreadFa.txt,
> 0005-split-flusher-executor-into-flushSorter-and-flushWrite.txt,
> screenshot-1.jpg
>
>
> Suggestion was made that
> http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryPoolMXBean.html#setCollectionUsageThreshold(long)
> is relevant. Correlation eludes me, but I Am Not A Java Expert. :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
