Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "FAQ" page has been changed by PeterSchuller. The comment on this change is: Be slightly less thrift-centric. http://wiki.apache.org/cassandra/FAQ?action=diff&rev1=96&rev2=97 -------------------------------------------------- * [[#slows_down_after_lotso_inserts|Why does Cassandra slow down after doing a lot of inserts?]] * [[#existing_data_when_adding_new_nodes|What happens to existing data in my cluster when I add new nodes?]] * [[#modify_cf_config|Can I add/remove/rename Column Families on a working cluster?]] - * [[#node_clients_connect_to|Does it matter which node a Thrift client connects to?]] + * [[#node_clients_connect_to|Does it matter which node a Thrift or higher-level client connects to?]] * [[#what_kind_of_hardware_should_i_use|What kind of hardware should I run Cassandra on?]] * [[#architecture|What are SSTables and Memtables?]] * [[#working_with_timeuuid_in_java|Why is it so hard to work with TimeUUIDType in Java?]] @@ -84, +84 @@ <<Anchor(node_clients_connect_to)>> - == Does it matter which node a Thrift client connects to? == + == Does it matter which node a Thrift or higher-level client connects to? == - No, any node in the cluster will work; Cassandra nodes proxy your request as needed. This leaves you with a number of options for end point selection: + No, any node in the cluster will work; Cassandra nodes proxy your request as needed. This leaves the client with a number of options for end point selection: 1. You can maintain a list of contact nodes (all or a subset of the nodes in the cluster), and configure your clients to choose among them. 1. Use round-robin DNS and create a record that points to a set of contact nodes (recommended). 1. Use the `get_string_property("token map")` RPC to obtain an update-to-date list of the nodes in the cluster and cycle through them. 1. Deploy a load-balancer, proxy, etc. + + When using a higher-level client you should investigate which, if any, options are implemented by your higher-level client to help you distribute your requests across nodes in a cluster. <<Anchor(what_kind_of_hardware_should_i_use)>>
