what's next after adding 3 new nodes not as the steps of “Starting multiple new nodes”?

hi, all I added 3 new nodes into my old cassandra cluster, every time I waited bootstrap on one node to complete before running bootstrap on another one, and now, I get the normal status when running nodetool status, and I can execute insert and select operations. But when I read Starting

Re: cassandra database design

Thanks,Carlos. the key point is how to balance the data spread around the cluster and the partition number of query. it is hard to determine which is best.anyway,thanks for your suggestion.it help me a lot. stone On Thu, Sep 1, 2016 at 4:54 PM, Carlos Alonso wrote: > I

Re: cassandra schema initialization in docker

Actually, I was advocating keeping the data directory outside of the container and using docker volumes to mount the existing files. You would add something like this to your docker run: -v /data:/var/cassandra/data As explained here: https://docs.docker.com/engine/tutorials/dockervolumes/

Re: cassandra schema initialization in docker

Thank you. Maybe it does make sense to put these sstables inside docker image, what will I lose in this case? On Sep 2, 2016 12:28 AM, "Patrick McFadin" wrote: > You can create a custom endpoint script that you will need to add with a > docker build. In that script you'll

Re: cassandra schema initialization in docker

You can create a custom endpoint script that you will need to add with a docker build. In that script you'll have to do do a wait loop for when c* is up and running. Being a little more creative, you could pre-bake some sstables and then use docker volumes to mount /data on a local file system.

Re: cassandra schema initialization in docker

Thanks. As for production I will do it in another way, it is just for development purposes to provide an easy way to run application on local machine. On Sep 1, 2016 10:26 PM, "Jonathan Haddad" wrote: > I wouldn't recommend blindly executing CQL statements on startup in a >

Re: cassandra schema initialization in docker

I wouldn't recommend blindly executing CQL statements on startup in a production cluster, IF NOT EXISTS or not. Those statements don't use LWT or anything See https://issues.apache.org/jira/browse/CASSANDRA-8387 On Thu, Sep 1, 2016 at 12:22 PM Michael Mior wrote: > This is

Re: cassandra schema initialization in docker

This is really more of a Docker question than a Cassandra question but if you include the CQL file in your Docker image, you could just change the CMD line in your Dockerfile to run the script after starting Cassandra. You would probably need to add a delay and some retries to ensure the server

Re: cassandra schema initialization in docker

I accept both cases. Second will work because I use create if not exists. 2016-09-01 21:02 GMT+03:00 Michael Mior : > I'm not sure I understand what you're trying to do. Do you want this to be > executed once when the container is built or every time the container is >

Re: cassandra schema initialization in docker

I'm not sure I understand what you're trying to do. Do you want this to be executed once when the container is built or every time the container is started? -- Michael Mior michael.m...@gmail.com 2016-09-01 13:57 GMT-04:00 Vova Shelgunov : > Sorry, I did not specify, that I

Re: cassandra schema initialization in docker

Sorry, I did not specify, that I need to execute cql right after cassandra container start. 2016-09-01 20:52 GMT+03:00 Michael Mior : > You should just be able to connect to the Cassandra instance and execute > CQL as you would against any other Cassandra installation. Any

Re: cassandra schema initialization in docker

You should just be able to connect to the Cassandra instance and execute CQL as you would against any other Cassandra installation. Any applications wishing to use the Cassandra instance inside the container will require the port to be exposed somehow anyway. -- Michael Mior

cassandra schema initialization in docker

Hi, I wonder if anyone can suggest a way how to initialize application schema to cassandra inside docker container (e.g. by executing cql file). Is there a way? Thanks, Uladzimir

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

There should be a corresponding error and stacktrace in your cassandra logs on 10.0.230.25. Please find that and post it, if you can. On Thu, Sep 1, 2016 at 7:23 AM, Siddharth Verma < verma.siddha...@snapdeal.com> wrote: > Debugged the issue a little. > AbstractFuture.get() throws

Re: nodetool repair uses option '-local' and '-pr' togather

Thanks for the info, Paulo. My cluster is in AWS, the keyspace has replication factor 3 with NetworkTopologyStrategy in one DC which have 5 nodes: 2 in us-east-1b, 2 in us-east-1c and 1 in us-east-1d. If I understand the way replication is done, the node in us-east-1d has all the (data) replicas,

Re: nodetool repair uses option '-local' and '-pr' togather

https://issues.apache.org/jira/browse/CASSANDRA-7450 2016-09-01 13:11 GMT-03:00 Li, Guangxing : > Hi, > > I have a cluster running 2.0.9 with 2 data centers. I noticed that > 'nodetool repair -pr keyspace cf' runs very slow (OpsCenter shows that the > node's data size

nodetool repair uses option '-local' and '-pr' togather

Hi, I have a cluster running 2.0.9 with 2 data centers. I noticed that 'nodetool repair -pr keyspace cf' runs very slow (OpsCenter shows that the node's data size is 39 GB and the largest SSTable size is like 7 GB so the column family is not huge, SizeTieredCompactionStrategy is used). Repairing

Re: Read timeouts on primary key queries

Have you looked at cfhistograms/tablehistograms your data maybe just skewed (most likely explanation is probably the correct one here) Regard, Ryan Svihla _ From: Joseph Tech Sent: Wednesday, August 31, 2016 11:16 PM Subject:

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Debugged the issue a little. AbstractFuture.get() throws java.util..concurrent.ExecutionException in, Uninterruptables.getUninterruptibly interrupted gets set to true, which does Thread.interrupt() thus in DefaultResultSetFuture (ResultSet)Uninterruptibles.getUninterruptibly(this) throws

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Correction : java driver version : 3.1.0

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Update : I page on the ResultSet explicitly in the program( *boundStatement.setPagingState(PagingState.fromString(currentPageInfo));*) When i put a *limit 10* after select statement, there is no error, with the token range set i provided it However, without that, there is this error, on second

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Hi Ben 1. cassandra 3.6 2. driver 3.2 3. Statement : select * from my_ks.my_table1 where token(pk1) >= ? and token(pk1) https://play.google.com/store/apps/details?id=com.snapdeal.main_source=mobileAppLp_campaign=android> [image: A]

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Hi Siddarth, It would probably help people provide and answer if you let everyone some more details like: - cassandra version and driver version you are using - query that is being executed when the error occurs - schema of the table that is being queried Cheers Ben On Thu, 1 Sep 2016 at 21:19

ServerError: An unexpected error occurred server side; in cassandra java driver

Hi, Could someone help me out with the following exception in cassandra java driver. Why did it occur? MyClass program is paging on the result set. com.datastax.driver.core.exceptions.ServerError: An unexpected error occurred server side on /10.0.230.25:9042: java.lang.AssertionError:

Re: Question about end of life support for Apache Cassandra 2.1 and 2.2

"unsupported" means there won't be any more release, so no more patches whatsoever and you're on your own. On Thu, Sep 1, 2016 at 12:09 AM, Anmol Sharma wrote: > According to the download page, > Apache Cassandra 2.1 is

Re: testing retry policy

On Wed, Aug 31, 2016 at 6:56 PM, Jimmy Lin wrote: > hi all, > I have some customized retry policies that want to test. > In my single node local cluster, is there anyway to simulate the > read/write timeout and or unavailable exception? > I tried to kill the Cassandra

Re: cassandra database design

I guess there's no easy solution for this. The bucketing technique you were applying with the publish_pre extra field making a composite partition key is probably your best bet but you're right being concerned that all your workload will hit the same node during an hour. I'd then suggest adding a

Re: Guidelines for configuring Thresholds for Cassandra metrics

Hi Ryan, Thank you for the exhaustive list of params to monitor and for your detailed reply. It will definitely help. Nagaraj, We are planning to use ManageEngine Application Manager to monitor Cassandra Instances. Scott, We will try out this tool as well. Best Regards,

STCS Compaction with wide rows & TTL'd data

We're running C* 1.2.11 and have two CFs, one called OAuth2AccessToken and one OAuth2AccessTokensByUser. OAuth2AccessToken has the token as the row key, and the columns are some data about the OAuth token. There's a TTL set on it, usually 3600, but can be higher (up to 1 month).