Stream session's index build waiting to be scheduled
2015-05-29 09:55:09 GMT
Evening list, Simple and quick question, can anyone point me to where the Cassandra 1.2.x series EOL date was announced? I see archived mailing list threads for 1.2.19 mentioning it was going to be the last release and I see CVE-2015-0225 mention it is EOL. I didn't see it say when the official EOL date was. Thanks! Jason
I’ve been investigating using replace_address to replace a node that hasn’t left the cluster cleanly and after upgrading from 2.1.0 to 2.1.4 it seems that adding a new node will automatically replace an existing node with the same IP address even if replace_address isn’t used. Does anyone know whether this is an expected change (as far as I can tell it doesn’t seem to be)?
I’ve been hitting this by
· creating a two node cluster (with the nodes in different datacentres)
· blocking traffic between the two nodes
· decommissioning one of them
· unblocking traffic between the two nodes
· trying to re-add the decommissioned node back into the cluster.
I reproduced this with some extra logging and it seems this change was introduced by CASSANDRA-7939 in 2.1.1. When StorageService.checkForEndpointCollision calls Gossiper.isFatClient TokenMetadata.tokenToEndpointMap is empty so isFatClient returns true.
As I understand, the Spark SQL Thrift/JDBC server cannot be used with the open source C*. Only DSE supports the Spark SQL JDBC server.
We would like to find out whether how many organizations are using this combination. If you do use DSE + Spark SQL JDBC server, it would be great if you could share your experience. For example, what kind of issues you have run into? How is the performance? What reporting tools you are using?
Hello. I'm reading "Beginning Apache Cassandra Development" and there are a few things I can't figure out. First. Lets say I have a table (field1, field2, field3, field4), where (field1, field2) is a primary key and field1 is partition key. There is a secondary index for field3 column. Do I right understand that in this case query like: select ... from my_table where field1 = 123 and field3 > '...'; ... would be quite efficient, i.e. request would be send only to one node, not the whole cluster? Second. Lets say there is some data that almost never changes but is read all the time. E.g. information about smiles in social network. Or current sessions. In this case would Cassandra cache "hot" data in memtable? Or such data should be stored somewhere else, i.e. Redis or Couchbase? -- -- Best regards, Eax Melanhovich http://eax.me/
We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8 weeks. In the meantime, I have been lent a single server that I can use. I am wondering what the best way is to set up my single node (SN), so I can then move to the 3-node cluster (3N) when the hardware arrives.
1. Create my keyspaces on SN with RF=1, and when 3N is up and running migrate all the data manually (either through Spark, dump-and-load, or write a small script)?
2. Create my keyspaces on SN with RF=3, bootstrap the 3N nodes into a 4-node cluster when they’re ready, then remove SN from the cluster?
3. Use SN as normal, and when 3N hardware arrives, physically move the data folder and commit log folder onto one of the nodes in 3N and start it up as a seed?
4. Any other recommended solutions?
I’m not even sure what the impact would be of running a single node with RF=3 – would this even work?
Any ideas would be much appreciated.