[
https://issues.apache.org/jira/browse/CASSANDRA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-622.
--------------------------------------
Resolution: Duplicate
moved the still-relevant multithreading part to CASSANDRA-3578
> Improve commitlog performance
> -----------------------------
>
> Key: CASSANDRA-622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-622
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Priority: Minor
> Labels: gsoc, gsoc2010
>
> Postgresql uses fixed-size commitlog files that it pre-allocates (filling
> with zeros) so "appending" to the log can use cheaper fsync-without-metadata
> (length changes is "metadata"). Then, when a commitlog is not needed, it
> "recycles" it by renaming it to a higher number. Commitlog entries have an
> increasing id, and if you come to an out-of-sequence (earlier) id, then you
> must have have reached the end of the commitlog and are reading from the
> "recycled" part.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
