cassandra-3.0

问题 I want to use batch statement to delete a row from 3 tables in my database to ensure atomicity. The partition key is going to be the same in all the 3 tables. In all the examples that I read about batch statements, all the queries were for a single table? In my case, is it a good idea to use batch statements? Or, should I avoid it? I'm using Cassandra-3.11.2 and I execute my queries using the C++ driver. 回答1: Yes, you can use batch to ensure atomicity. Single partition batches are faster

问题 Can I create different runtime versions (containers w.r.t. different configurations) from same image? Eg. in Cassandra, a distributed database, each node in the ring (cluster) of Cassandra needs to know information about other nodes during bootstrap (eg. the seed address). This information is picked from cassandra.yaml file. How can I change this cassandra.yaml file for each container when the container starts? For example, I suppose the steps to make an image could be download cassandra.tar

问题 I manually cassandra which works fine (Standalone). Now I am experimenting with installing cassandra using docker . I downloaded Cassandra image using command (following the steps on https://hub.docker.com/_/cassandra) docker pull 3.11.4 I am able to start the images using docker run image_id The images listens on Starting listening for CQL clients on /0.0.0.0:9042 (unencrypted)... but I am not able to connect to it using cqlsh of my Standalone but it is not able to connect with it. C:\Users

问题 Im trying to start DSE 5.0.1 Cassandra (Single node) in my local. Getting below error: CassandraDaemon.java:698 - Cannot start node if snitch's data center (Cassandra) differs from previous data center (Graph). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true 回答1: If you are using GossipingPropertyFileSnitch, start Cassandra with the option -Dcassandra.ignore_dc=true If it starts successfully, execute: nodetool repair

问题 I have an old Cassandra cluster that I want to get rid of, and want to transfer data from only few selected tables from old cluster to a new one that I have created. I have tried using Cassandra's COPY command on a table that has about 15 million rows (approx 20 columns for each row). When I try to import data from the csv file to the same table in our new cluster, I am getting this response constantly : Failed to import 20 rows: WriteTimeout - Error from server: code=1100 [Coordinator node

问题 I have 2 nodes ip1 node1's ip ip2 nodes2's ip each node starting but not connecting each other.. For example nodetool status show own node. Not other node in node1's log: Handshaking version with /ip2 in node2's log there are no info or error messages related to node1 no error messages both of them. What causes this problem? 回答1: A node should not normally be in its own seed list; if it is, it will not try to join the existing cluster. Only the first node in a cluster should be in its own

问题 I have 2 nodes ip1 node1's ip ip2 nodes2's ip each node starting but not connecting each other.. For example nodetool status show own node. Not other node in node1's log: Handshaking version with /ip2 in node2's log there are no info or error messages related to node1 no error messages both of them. What causes this problem? 回答1: A node should not normally be in its own seed list; if it is, it will not try to join the existing cluster. Only the first node in a cluster should be in its own

问题 I have 2 nodes ip1 node1's ip ip2 nodes2's ip each node starting but not connecting each other.. For example nodetool status show own node. Not other node in node1's log: Handshaking version with /ip2 in node2's log there are no info or error messages related to node1 no error messages both of them. What causes this problem? 回答1: A node should not normally be in its own seed list; if it is, it will not try to join the existing cluster. Only the first node in a cluster should be in its own

问题 From cassandra's documentation I got to know that cassandra uses timestamps of query to resolve conflicts between two writes and hence the clocks on all the nodes of the cluster needs to be synchronised. In my use-case we have only one client writing to the cluster and multiple clients reading from the cluster. So, if I use client-side timestamp generator (which I believe is default for version>3) do I still need to have cluster node clocks synchronised with each other? 回答1: In the context of

问题 I have a single node Cassandra cluster which hits to ReadTimeOutException and I observe the following logs in server which seems weird to me, ERROR [SharedPool-Worker-91] 2018-05-29 12:09:53,023 ErrorMessage.java:338 - Unexpected exception during request java.lang.RuntimeException: org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - received only 1 responses. at org.apache.cassandra.auth.CassandraRoleManager.getRole(CassandraRoleManager.java:489) ~[apache-cassandra-3.0