You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/14 00:30:12 UTC

[jira] [Resolved] (CASSANDRA-3321) Node joins/Node moves should build caches

     [ https://issues.apache.org/jira/browse/CASSANDRA-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-3321.
---------------------------------------

    Resolution: Duplicate

duplicate of CASSANDRA-2443
                
> Node joins/Node moves should build caches 
> ------------------------------------------
>
>                 Key: CASSANDRA-3321
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3321
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Edward Capriolo
>            Priority: Minor
>
> Cassandra use case: high rate of low latency reads served mostly from caches. When a new node is joined data is streamed to it. However it is born into a 'cold world'. It does not have the benefit of saved caches. Clients with auto-discovery will find it and start sending requests it's way. If the request rate is high enough and clients are aggressive enough the Cassandra node could run out of sockets. This feature would build 'best effort' caches possibly by sampling entries from the caches of nodes the data was streamed from. With this even a newly joined node should have cache warming.

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