cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-622) better commitlog performance
Date Mon, 18 Jan 2010 19:22:54 GMT


Jonathan Ellis updated CASSANDRA-622:

    Fix Version/s:     (was: 0.6)

> better commitlog performance
> ----------------------------
>                 Key: CASSANDRA-622
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Priority: Minor
> 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"

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message