cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-2069) Read repair causes tremendous GC pressure
Date Tue, 08 Feb 2011 05:03:02 GMT


Jonathan Ellis updated CASSANDRA-2069:

    Attachment: 2069.txt

bq. RR does not appear to actually occur

No digest reads are being sent but I don't know why.  v8 adds better debug logging around
ReadCallback.endpoints creation which governs that.

> Read repair causes tremendous GC pressure
> -----------------------------------------
>                 Key: CASSANDRA-2069
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.1
>            Reporter: Brandon Williams
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.2
>         Attachments: 2069-v2.txt, 2069-v3.txt, 2069-v4.txt, 2069-v5.txt, 2069-v6.txt,
2069-v7.txt, 2069-v8.txt, 2069.txt
> To reproduce: start a three node cluster, insert 1M rows with and rf=2. 
Take one down, delete its data, then bring it back up and issue 1M reads against it.  After
the run is done you will see at least 1 STW long enough to mark the node as dead, often 4
or 5.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message