cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3155) Secondary index should report it's memory consumption
Date Thu, 22 Dec 2011 21:39:31 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175083#comment-13175083
] 

Jonathan Ellis commented on CASSANDRA-3155:
-------------------------------------------

This feels clunky to me.  Wouldn't it be better to have both CFS and non-CFS indexes provide
the same API so we can do it polymorphically w/ a single loop?
                
> Secondary index should report it's memory consumption
> -----------------------------------------------------
>
>                 Key: CASSANDRA-3155
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3155
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>            Reporter: Jason Rutherglen
>            Assignee: T Jake Luciani
>            Priority: Minor
>             Fix For: 1.0.7
>
>         Attachments: v1-0001-CASSANDRA-3155-non-cfs-backed-indexes-report-live-memo.txt
>
>
> Non-CFS backed secondary indexes will consume RAM which should be reported back to Cassandra
to be factored into it's flush by RAM amount.

--
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

        

Mime
View raw message