cassandra-client-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul "LeoNerd" Evans <leon...@leonerd.org.uk>
Subject Re: Multi-node cluster-aware client connection
Date Wed, 11 Sep 2013 21:52:23 GMT
On Wed, 11 Sep 2013 17:20:16 +0100
Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote:

>  1. What is a good way to handle prepared statements here? Should they
>     be prepared on all the (primary/all?) nodes, or just one? Some
>     applications I could imagine having just a handful of heavily-used
>     prepared statements, so they'd become a hotspot on one node if it
>     wasn't spread around. But then what to do as new nodes become
>     elected as primaries? Should they be prepared eagerly on
>     connection? Lazily at next use?

So a careful reading of the python client [1] suggests that it's just
storing a single statement ID for the prepared statement across the
cluster. I have also found this

  https://issues.apache.org/jira/browse/CASSANDRA-4449

which requests is be a single global ID across the cluster, rather than
per node. Is this now the case then - does the statement have a single
ID across the entire cluster? Can I rely on this? In this case, do I
still have to prepare it on the other nodes, or is a single node
sufficient?

[1]: https://github.com/datastax/python-driver/tree/master/cassandra

-- 
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/

Mime
View raw message