RE: all the nost are not reacheable when running massive deletes

2016-04-11 Thread Paco Trujillo
C*heers, --- Alain Rodriguez - al...@thelastpickle.com<mailto:al...@thelastpickle.com> France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2016-04-07 9:18 GMT+02:00 Paco Trujillo mailto:f.truji...@genetwister.nl>>: Well, then you could trying

RE: all the nost are not reacheable when running massive deletes

2016-04-07 Thread Paco Trujillo
run any streaming process (repairs / bootstrap / node removal) during the upgrade and while you have not yet run "nodetool upgradesstable". There is a lot of informations out there about upgrades. C*heers, --- Alain Rodriguez - al...@thelastpickle.com<mai

RE: nodetool drain running for days

2016-04-06 Thread Paco Trujillo
n the version you’re running. From: Paco Trujillo Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" Date: Tuesday, April 5, 2016 at 11:12 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" Subject: nodetool drain running for day

RE: Cassandra Single Node Setup Questions

2016-04-06 Thread Paco Trujillo
The fact that there is one single DC does not mean that you do not need multiples nodes. Without multiples nodes you do not have redundancy (the nodes fail and you lose the database) and you cannot scale the cluster if the number of users and/or rows grows adding more nodes unless you have test

RE: Cassandra Single Node Setup Questions

2016-04-06 Thread Paco Trujillo
When we start using cassandra in our company, we decide to use a single node Cassandra cluster as PoC. Everything was correct until we really need the power of a Cassandra cluster and then our data models were not appropriate for a cluster with multiple nodes because of redundancy, data access p

nodetool drain running for days

2016-04-05 Thread Paco Trujillo
We are having performance problems with our cluster regarding to timeouts when repairs are running or massive deletes. One of the advice I received was update our casssandra version from 2.0.17 to 2.2. I am draining one of the nodes to start the upgrade and the drain is running now for two days.

RE: all the nost are not reacheable when running massive deletes

2016-04-05 Thread Paco Trujillo
running massive deletes Network issues. Could be jumbo frames not consistent or other. sent from my mobile sent from my mobile Daemeon C.M. Reiydelle USA 415.501.0198 London +44.0.20.8144.9872 On Apr 4, 2016 5:34 AM, "Paco Trujillo" mailto:f.truji...@genetwister.nl>> wrote: Hi

RE: all the nost are not reacheable when running massive deletes

2016-04-05 Thread Paco Trujillo
om> France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2016-04-04 14:33 GMT+02:00 Paco Trujillo mailto:f.truji...@genetwister.nl>>: Hi everyone We are having problems with our cluster (7 nodes version 2.0.17) when running “massive deletes” on one of the nod

all the nost are not reacheable when running massive deletes

2016-04-04 Thread Paco Trujillo
Hi everyone We are having problems with our cluster (7 nodes version 2.0.17) when running "massive deletes" on one of the nodes (via cql command line). At the beginning everything is fine, but after a while we start getting constant NoHostAvailableException using the datastax driver: Caused by

timout connections from opscenter

2015-08-17 Thread Paco Trujillo
Hi Our opscenter can not connect to the nodes, in the logs the next error appears: 2015-08-17 08:56:37+0200 [SNPaware_Cluster] INFO: Nodes with agents that appear to be no longer running: 172.31.7.245, 172.31.7.244, 172.31.7.247, 172.31.7.246, 172.31.7.243 2015-08-17 08:56:37+0200 [SNPaware_Cl

RE: clean Opscenter info for cluster

2015-08-16 Thread Paco Trujillo
Hi At the end, we have solved the problem deleting also the Opscenter keyspace from the cluster and restarting the opscenter. Then the retry attemps to the old nodes in the cluster disappeared. From: Paco Trujillo [mailto:f.truji...@genetwister.nl] Sent: maandag 17 augustus 2015 08:29 To: user

clean Opscenter info for cluster

2015-08-16 Thread Paco Trujillo
Hi We were having some issues with different versions in our cluster and the info which appear in Opscenter. We decide to delete the datastax-agents in each of the nodes and delete the cluster from the opscenter. But I still see on the opscenter logs attemps to retry connections to the nodes o

RE: How do you run integration tests for your cassandra code?

2014-10-13 Thread Paco Trujillo
Hi Kevin We are using a similar solution than horschi. In the past we use CassandraUnit (https://github.com/jsevellec/cassandra-unit) but truncate the tables after and before each test works better for us. We also set gc_grace_seconds to zero. From: horschi [mailto:hors...@gmail.com] Sent: maa

RE: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with changed partitioner settings

2014-07-29 Thread Paco Trujillo
Hi tsi We faced a similar situation a few months ago. At the end what we make is developed a service in our application to migrate the data from the old cassandra 1.2 to the new cassandra 2.0 using cql (with normal SELECT and UPDATE commands) (our application at that moment have two cassandra s

RE: Select with filtering

2014-04-25 Thread Paco Trujillo
Hi Mikhail It is not a bug/not implemented feature and you are not doing nothing wrong. As you can check on the documentation you can only filter on a key name or a column that has a secondary index created on it: http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/select_r.html F

RE: Centralized tool to install and manage C* from one machine

2014-01-27 Thread Paco Trujillo
Hi To manage the cluster we are using the OpsCenter, it is a free web tool from Datastax that allow you basic execute basic operations in any node on the cluster. It also contain differents metrics which you can add to a kind of dashboard and monitoring the most important parameters in the clus

thrift_max_message_length_in_mb is not recognized by cassandra-cli

2013-10-15 Thread Paco Trujillo
Hi everyone I am having problems trying to query a wide row in Cassandra 1.2.4 When I tried to query the row using the Cassandra-cli, I obtain this error: Frame size (75209759) larger than max length (15728640)! org.apache.thrift.transport.TTransportException: Frame size (75209759) larger than