Re: How many BATCH inserts in to many?

Hello, I have managed to insert up to 63k records without any problem. In certain workloads I found that massive batch inserts perform way better than lots of not-so-massive inserts. I guess it also depends on your setup. Just try it. Alan Ristić alan.ris...@gmail.com escreveu: Hi, I'm

Client Timeouts on incrementing counters

. I'm bagging my head against the wall checking where can I tune Cassandra to get rid of this error! Thx, Carlos Rolo

RE: Client Timeouts on incrementing counters

from the upgrade? I just did a rolling restart of all nodes one-by-one. From: Tyler Hobbs [mailto:ty...@datastax.com] Sent: vrijdag 11 november 2011 20:18 To: user@cassandra.apache.org Subject: Re: Client Timeouts on incrementing counters On Fri, Nov 11, 2011 at 7:17 AM, Carlos Rolo c.r

RE: cassandra most stable version ?

Hi Pierre, Using 1.0.2 without any problem so far. 0.8.x had problems for us. Never tried 0.8.7 or later tough. Carlos Rolo From: Karsten Pappert [mailto:kars...@pappert.de] Sent: woensdag 7 december 2011 16:54 To: user@cassandra.apache.org; pie...@chalamet.net Subject: AW: cassandra most

Added nodes to cluster, authentication stopped working

Hi all, I have a Cassandra Cluster running and we recently duplicated the cluster. After following all the steps, the cassandra clients started failing with the following message: AuthenticationException(why='Username and/or password are incorrect') The problem is that even I can't login to

Re: Upgrading from 1.2 to 2.1 questions

Using Pycassa (https://github.com/pycassa/pycassa)I had no trouble with the Clients writing/reading from 1.2.x to 2.0.x (Can't recall the minor versions out of my head right now). Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo |

Re: Newly added column not visible

Hey Saurabh, Your issue seems similar to one I have, but mine seems like a timing issue (and not easy to reproduce) , check the comments here https://issues.apache.org/jira/browse/CASSANDRA-8012 and see if it fits your problem. Otherwise do like Mark recommended and create a new JIRA issue.

Re: Anonymous user in permissions system?

Hello Erik, It seems possible, refer to the following documentation to see if it fits your needs: http://www.datastax.com/documentation/cassandra/2.0/cassandra/security/secureInternalAuthenticationTOC.html

Re: how to batch the select query to reduce network communication

Hi, You can't. Batches are only available for INSERT, UPDATE and DELETE operations. Batches exist to give Cassandra some atomicity, as in, or all operations succeed or all fail. Regards, Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo

Re: Adding new node - OPSCenter problems

Hello, What is the output of nodetool status? All nodes should appear, otherwise there is some configuration error. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo

Re: Many pending compactions

Hi 100% in agreement with Roland, 2.1.x series is a pain! I would never recommend the current 2.1.x series for production. Clocks is a pain, and check your connectivity! Also check tpstats to see if your threadpools are being overrun. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian

Re: C* 2.1.2 invokes oom-killer

So compaction doesn't seem to be your problem (You can check with nodetool compactionstats just to be sure). How much is your write latency on your column families? I had OOM related to this before, and there was a tipping point around 70ms. -- --

Re: C* 2.1.2 invokes oom-killer

rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo http://linkedin.com/in/carlosjuzarterolo* Tel: 1649 www.pythian.com On Thu, Feb 19, 2015 at 10:49 AM, Michał Łowicki mlowi...@gmail.com wrote: On Thu, Feb 19, 2015 at 10:41 AM, Carlos Rolo r...@pythian.com wrote: So

Re: C* 2.1.2 invokes oom-killer

trickle_fsync_interval_in_kb: 10240 On Thu, Feb 19, 2015 at 12:12 PM, Michał Łowicki mlowi...@gmail.com wrote: On Thu, Feb 19, 2015 at 11:02 AM, Carlos Rolo r...@pythian.com wrote: Do you have trickle_fsync enabled? Try to enable that and see if it solves your problem, since you are getting out of non-heap memory

Re: can't delete tmp file

You should upgrade to 2.1.3 for sure. Check the changelog here: https://git1-us-west.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.1.3 Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo |

Re: run cassandra on a small instance

of output. Thanks Tim On Thu, Feb 19, 2015 at 3:40 AM, Carlos Rolo r...@pythian.com wrote: I have Cassandra instances running on VMs with smaller RAM (1GB even) and I don't go OOM when testing them. Although I use them in AWS and other providers, never tried Digital Ocean. Does Cassandra just

Re: Upgrading from Cassandra 1.2.14 to Cassandra 2.10

is not compatible with 1.2.x ? Regards Charles From: Carlos Rolo r...@pythian.com Reply-To: user@cassandra.apache.org user@cassandra.apache.org Date: Thursday, 29 January 2015 14:47 To: user@cassandra.apache.org user@cassandra.apache.org Subject: Re: Upgrading from Cassandra 1.2.14

Re: Cassandra 2.0.11 with stargate-core read writes are slow

HI Asit, The only help I'm going to give is on point 3), as I have little experience with 2) and 1) depends on a lot of factors. For testing the workload use this: http://www.datastax.com/documentation/cassandra/2.1/cassandra/tools/toolsCStress_t.html It probably covers all your testing needs.

Re: nodetool status shows large numbers of up nodes are down

Hi Cheng, Are all machines configured with NTP and all clocks in sync? If that is not the case do it. If your clocks are not in sync it causes some weird issues like the ones you see, but also schema disagreements and in some cases corrupted data. Regards, Regards, Carlos Juzarte Rolo

Re: best supported spark connector for Cassandra

Not for sure ;) If you need Cassandra support I can forward you to someone to talk to at Pythian. Regards, Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo

Re: Two problems with Cassandra

Hello Pavel, What is the size of the Cluster (# of nodes)? And you need to iterate over the full 1TB every time you do the update? Or just parts of it? IMO information is short to make any kind of assessment of the problem you are having. I can suggest to try a 2.0.x (or 2.1.1) release to see

Re: nodetool status shows large numbers of up nodes are down

and request_timeout) from 3 to 1 for 6 nodes yesterday. Will this affect internode gossip? Thanks, Cheng On Mon, Feb 9, 2015 at 11:07 PM, Carlos Rolo r...@pythian.com wrote: Hi Cheng, Are all machines configured with NTP and all clocks in sync? If that is not the case do it. If your clocks

Re: Two problems with Cassandra

memory (8 or 16 GB) it dies much faster due to GC not being able to keep up. But it consistently dies on a specific row in single instance case… Is this enough info to point me somewhere? Thank you, Pavel On Feb 11, 2015, at 1:48 PM, Carlos Rolo r...@pythian.com wrote: Hello Pavel

Re: Upgrade from 2.0.9 to 2.1.3

I would not recommend an upgrade to 2.1.x for now. Do you have any specific reason to upgrade? For upgrading from 2.0.9 you can just do a direct upgrade. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: Replication to second data center with different number of nodes

Sharing my experience here. 1) Never had any issues with different size DCs. If the hardware is the same, keep the # to 256. 2) In most of the cases I keep the 256 vnodes and no performance problems (when they are triggered, the cause is not the vnodes #) Regards, Carlos Juzarte Rolo Cassandra

Re: Unexplained query slowness

You can use query tracing to check what is happening. Also you fire jconsole/JavaVisualVM and push out some metrics like the 99th read Beans for that column family. A simpler check is using cfstats and look for weird numbers (high number sstables, if you are deleting check how much tombstones per

Re: Setting up JNA on CentOS 6.6. with cassandra20-2.0.12 and Oracle Java 1.7.0_75

Hello, I always install JNA into the lib directory of java itself Since I normally have java in /opt/java I put the JNA into /opt/java/lib. ~$ grep JNA /var/log/cassandra/system.log INFO HH:MM:SS JNA mlockall successful Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your

Re: Setting up JNA on CentOS 6.6. with cassandra20-2.0.12 and Oracle Java 1.7.0_75

Also I always install JNA from the JNA page. I did the installation for this blog post in CentOS 6.5: http://www.pythian.com/blog/from-0-to-cassandra-an-exhaustive-approach-to-installing-cassandra/ Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian |

Re: AMI to use to launch a cluster with OpsCenter on AWS

Regarding AWS the only thing I normally do (besides the normal installation, etc) is setting up the firewall zones so the ports needed for Cassandra are open. You can follow this guide: https://razvantudorica.com/02/create-a-cassandra-cluster-with-opscenter-on-amazon-ec2/a Regards, Carlos

Re: Possible problem with disk latency

Your latency doesn't seem that high that can cause that problem. I suspect more of a problem with the Cassandra version (2.1.3) than that with the hard drives. I didn't look deep into the information provided but for your reference, the only time I had serious (leading to OOM and all sort of weird

Re: Write timeout under load but Read is fine

What is the consistency level you are using? Are you using Thrift or CQL? Are you using SSDs? Check if compactions are running when you get the timeouts. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: What is 'Read Reuqests' on OpsCenter exaclty?

. A future version of OpsC will include tooltips with these descriptions for better clarity. On Apr 23, 2015 6:30 AM, Carlos Rolo r...@pythian.com wrote: Probably it takes in account the read repair, plus a read that have consistency != 1 will produce reads on other machines (which are taken

Re: Adding nodes to existing cluster

Start one node at a time. Wait 2 minutes before starting each node. How much data and nodes you have already? Depending on that, the streaming of data can stress on the resources you have. I would recommend to start one and monitor, if things are ok, add another one. And so on. Regards, Carlos

Re: Adding nodes to existing cluster

by one if we're not using rack awareness? On Mon, Apr 20, 2015 at 2:49 PM, Carlos Rolo r...@pythian.com wrote: Start one node at a time. Wait 2 minutes before starting each node. How much data and nodes you have already? Depending on that, the streaming of data can stress

Re: LCS Strategy, compaction pending tasks keep increasing

Are you on version 2.1.x? Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo http://linkedin.com/in/carlosjuzarterolo* Mobile: +31 6 159 61 814 | Tel: +1 613 565 8696 x1649 www.pythian.com On

Re: What is 'Read Reuqests' on OpsCenter exaclty?

Probably it takes in account the read repair, plus a read that have consistency != 1 will produce reads on other machines (which are taken in account). I don't know the internals of opscenter but I would assume that this is the case. If you want to test it further, disable read_repair, and make

Re: minimum bandwidth requirement between two Geo Redundant sites of Cassandra database

Hi, I would not recommend anything below 1Gbps for the bandwidth. Latency try to have it as low as you can. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo

Re: New node got stuck joining the cluster after a while

Hi, The 2.1.x series is not recommeded for use, especially the first versions. I would downgrade to 2.0.14 or if must stay on 2.1 upgrade your cluster to 2.1.4 or the imminent release of 2.1.5. This mailing list as a few tips how to deal with the 2.1.x releases, but the best way is indeed a

Re: Best practice: Multiple clusters vs multiple tables in a single cluster?

Adding a new keyspace should be perfectly fine. Unless you have completely distinct workloads for the different keyspaces. Even so you can balanced some stuff at keyspace/table level. But I would go with a new keyspace not with a new cluster given the small size you say you have. Regards, Carlos

Re: Reading too many tombstones

The TTL data will only be removed after the gc_grace_seconds. So your data with 30 days TTL will be still in Cassandra for 10 days more (40 in total). Is your data being there for more than that? Otherwise it is expected behaviour and probably you should do something on your data model to avoid

Re: Ghost compaction process

HI, Is it 2.0.14 or 2.1.4? If you are on 2.1.4 I would recommend an upgrade to 2.1.5 regardless of that issue. From the data you provide it is difficult to access what is the issue. If you are running with RF=2 you can always add another node and kill that one if that is the only node that shows

Re: How to interpret some GC logs

GC Logs are a weird science. I use a couple of resources to get through them. Regarding your question my 1.8.0_40 always have the first the -. I greped through 2h of logs, and on a test environment. I use the following set of options: -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintHeapAtGC

Re: Hundreds of sstables after every Repair

Hello, Do you have your clocks synced across your cluster? Are you using NTP and have it properly configured? Sometimes clock out of sync can trigger weird behaviour. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: Missing data

Hi Jean, The problem of that Warning is that you are reading too many tombstones per request. If you do have Tombstones without doing DELETE it because you probably TTL'ed the data when inserting (By mistake? Or did you set default_time_to_live in your table?). You can use nodetool cfstats to

Re: Replication in one datacetner only

Yes, set the replication factor of the keyspace to only use the datacenter you want. More information here: http://docs.datastax.com/en/cql/3.1/cql/cql_reference/create_keyspace_r.html Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo |

Re: Question about nodetool status ... output

Your data model also contributes to the balance (or lack of) of the cluster. If you have a really bad data partitioning Cassandra will not do any magic. Regarding that cluster, I would decommission the x.52 node and add it again with the correct configuration. After the bootstrap, run a cleanup.

Re: Lucene index plugin for Apache Cassandra

Seems like an interesting tool! What operational recommendations would you make to users of this tool (Extra hardware capacity, extra metrics to monitor, etc)? Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: compaction occurring very frequently

Hi, 2.1.x does have compaction issues. Upgrading to 2.1.6 should help you. You can also search this mailing list for some recommendations for that specific problem since it is a recurrent issue. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter:

Re: Error while adding a new node.

Indeed you should upgrade to 2.1.7. And then report if you are still facing problems. Versions up to 2.1.5 (in the 2.1.x series) are not considered stable. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: [MASSMAIL]Re: Error while adding a new node.

mlor...@uci.cu wrote: The recommended version to use is 2.1.5 because, like you Carlos said, 2.1.6 and 2.1.7 are very new to consider them like stable. On 02/07/15 08:55, Carlos Rolo wrote: Indeed you should upgrade to 2.1.7. And then report if you are still facing problems. Versions up

Re: Wrong peers

There is a bug in Jira related to this, it is not a driver issue, is a Cassandra issue. It is solved on 2.0.14 I think. I will post the ticket once I find it. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: Multiple cassandra instances per physical node

Hi, I also advice against multiple instances on the same hardware. If you have really big boxes why not virtualize? Other option is experiment with CCM. Although there are some limitations with CCM (ex: JNA is disabled) If you follow up on this I would to hear how it went. Em 21/05/2015 19:33,

Re: howto do sql query like in a relational database

Hello Anton, You need to look into Datastax Entreprise (DSE) Offering. It integrates Solr search which allows you to do searches like the one you mention. There are also some opensource projects doing this kind of integration, so its up to you. And as Oded mentioned Cassandra really shines on

Re: Seed gossip version error

That error should only occur when you have a mismatch between the Seed version and the new node version. Are you sure all your nodes are running in the same version? Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin:

Re: cassandra repair error

Hello, It seems that is a problem with Cassandra trying to delete a directory that is not empty. First time seeing this error. Are your harddrives with enough space and working correctly? Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo

Re: scylladb

com/in/carlosjuzarterolo>* Mobile: +351 91 891 81 00 | Tel: +1 613 565 8696 x1649 www.pythian.com On Wed, Nov 11, 2015 at 4:46 PM, Dani Traphagen <dani.trapha...@datastax.com > wrote: > Killer, @cjrolo. Will you update via this thread? > > On Wed, Nov 11, 2015 at 7:57 AM, Carlos R

Re: scylladb

Not yet, but not far from doing it. No rain here yet! :) On a more serious tone, should be done before end of the Month. -- --

Re: scylladb

I will not try until multi-DC is implemented. More than an month has passed since I looked for it, so it could possibly be in place, if so I may take some time to test it. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin:

Re: scylladb

On Thursday, November 5, 2015, Carlos Rolo <r...@pythian.com> wrote: > >> I will not try until multi-DC is implemented. More than an month has >> passed since I looked for it, so it could possibly be in place, if so I may >> take some time to test it. >> >> Reg

Re: any update about CASSANDRA-10420

Can you provide more information? The description is generic, driver version and a test case that the devs can use to reproduce the bug would be optimal. I'm not involved in the development of cassandra, but that bug description doesn't seem complete. Maybe it is a driver bug and not a Cassandra

Re: Removed node is not completely removed

Check system.peers table to see if the IP is still there. If so edit the table and remove the offending IP. You are probably running into this: https://issues.apache.org/jira/browse/CASSANDRA-6053 Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian |

Re: Unable to start one Cassandra node: OutOfMemoryError

Dealt with that recently, and the only solution that made it work was to increase heap sizes. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo *

Re: Cassandra is consuming a lot of disk space

You can check if the snapshot exists in the snapshot folder. Repairs stream sstables over, than can temporary increase disk space. But I think Carlos Alonso might be correct. Running compactions might be the issue. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data

Re: Latest stable release

I honestly go with 2.1.13 unless you need the features on 2.2.x. I would not recommend 3.x for now (unless you need the features). Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo |

Re: Do I have to use repair -inc with the option -par forcely?

+1 on what Alain said, but I do think if you are high enough on a 2.1.x (will look later) version you don't need to follow the documentation. It is outdated. Run a full repair, the you can start incremental repairs since the SSTables will have the metadata on them about the last repair. Wait

Re: Changing snitch from PropertyFile to Gossip

As long as the topology doesn't change, yes. Repair once you finish. Em 24/04/2016 13:23, "AJ" escreveu: > Is it possible to do this without down time i.e. run in mixed mode while > doing a rolling upgrade? -- --

Re: Most stable version?

.X? or > latest 2.2.x is recommended? > > Currently I use 2.2.5, but is the latest 2.1.13 recommended for production > use? > > Regards, > Satoshi > > > On Mon, Apr 18, 2016 at 11:45 PM, Carlos Rolo <r...@pythian.com> wrote: > >> Sorry to resurrect this now, but I d

Re: Changing snitch from PropertyFile to Gossip

r is there a specific reason? > > C*heers, > --- > Alain Rodriguez - al...@thelastpickle.com > France > > The Last Pickle - Apache Cassandra Consulting > http://www.thelastpickle.com > > 2016-04-24 15:44 GMT+02:00 Carlos Rolo <r...@pythian.com>

Re: Most stable version?

are you suggesting at some point there will be a stable train for 3? > (or that 3.x will be bumped to 4.0 when stable)? > > We're on 2.2.5 and haven't seen any major problems with it. > > -J > > > > Sent via iPhone > > On Apr 22, 2016, at 03:34, Carlos Rolo <r..

Re: IF EXISTS checks on all nodes?

Hello, As far as I know, lightweight transactions only apply to a single partition, so in your case it will only execute on the nodes responsible for that partition. And as a consequence, those nodes will all be in the same state when the transaction ends (If it would apply). Please refer to

Re: COPY TO export fails with

Hello, That is a lot of data to do an "COPY TO. If you want a fast way to export, and you're fine with Java, you can use Cassandra SSTableReader classes to read the sstables directly. Spark also works. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra

Re: Most stable version?

Sorry to resurrect this now, but I don't consider anything after 3.0.x stable. I wrote a blog post about this to be clear: https://www.pythian.com/blog/cassandra-version-production/ Use it and pick a version based on your needs. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax

Re: Global TTL vs Insert TTL

To reinforce Alain statement: "I would say that the unsafe part is more about using C* 3.9" this is key. You would be better on 3.0.x unless you need features on the 3.x series. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your

Re: Global TTL vs Insert TTL

erform >> optimization when compacting. >> >> For example if it can see than the maxTimestamp of an SSTable is older >> than the table Global TTL, the SSTable can be entirely dropped during >> compaction >> >> Using dynamic TTL at runtime, since Cassandra d

Re: Read exceptions after upgrading to 3.0.10

By any chances are you using the PHP/C++ driver? -- --

Re: Failure when setting up cassandra in cluster

If Ryan answer doesn't help, post Cassandra version. There is a bug with cql and some python version that would lead to that error. Also, please post "nodetool status". Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data

Re: Support/Consulting companies

https://www.pythian.com/ Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin: *linkedin.com/in/carlosjuzarterolo * Mobile:

Re: Join_ring=false Use Cases

Beware the Java Driver limitations around whitelisting IPs. Works fine in Python. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:

Re: Has anyone deployed a production cluster with less than 6 nodes per DC?

It depends on a lot of factors. What causes the cluster to get crazy? I/O, Network, CPU? I manage clusters of all sizes (even 3 nodes per DC) but it all depends on usage and configuration. Regards, Carlos Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect /

Re: WriteTimeoutException with LWT after few milliseconds

You can try to use TRACING to debug the situation, but for a LWT to fail so fast, the most probable cause is what you stated: "It is possible that there are concurrent inserts on the same PK - actually thats the reason why I use LWTs." AKA, someone inserted first. Regards, Carlos Juzarte Rolo

Re: Node always dieing

i3 are having those issues more than the other instances it seems. Not the first report I heard about. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:

Re: Drop tables takes too long

You have 4800 Tables in total? That is a lot of tables, plus MVs? or MVs are already considered in the 60*80 account? I would recommend to reduce the table number. Other thing is that you need to check your log file for GC Pauses, and how long those pauses take. You also might need to increase

Re: Archive node

I would not suggest to do that, because the new "Archive" node would be a new DC that you would need to build (Operational wise). You could also snapshot the old one once it finishes and use SSTableloader to push it into your Development DC. This way you have isolation from Production. Plus no

Re: Node always dieing

There was some issue with the i3 instances and Cassandra. Did you had this cluster running always on i3? On Apr 6, 2017 13:06, "Cogumelos Maravilha" wrote: > Limit Soft Limit Hard Limit > Units > Max cpu time unlimited

Re: too many compactions pending and compaction is slow on few tables

Is not a good idea to do LCS on spinning. Change to STCS, and reduce the compactors to 2 (if you have more than 2). Check if that helps. On Apr 7, 2017 20:18, "Matija Gobec" wrote: > It does as the "new" data, even if the values are the same, has new write > time

Re: c* updates not getting reflected.

What consistency are you using on those queries? On 11 Jul 2017 19:09, "techpyaasa ." wrote: > Hi, > > We have a table with following schema: > > CREATE TABLE ks1.cf1 ( pid bigint, cid bigint, resp_json text, status int, > PRIMARY KEY (pid, cid) ) WITH CLUSTERING ORDER BY

Re: cassandra OOM

To add some contribution to this thread, we have seen both cases. CMS easily outperforming G1 for the same Heapsize and the inverse too. On the same cluster different workloads (datacenter based) we have both collectors because of performance based on the workload. It would be good to colect this

Re: Cassandra Setup Question

Use networktopologystrategy as replication strategy and make sure you have dc1: 3 and dc2: 3. This way you have 3 replicas in each DC. On 23 Aug 2017 12:53, "Jonathan Baynes" wrote: > Hi Community, > > > > Quick question regarding Replication Factor. > > > > In

Re: Adding a new node with the double of disk space

...@reddit.com.invalid> > wrote: > >> Are you saying if a node had double the hardware capacity in every way it >> would be a bad idea to up num_tokens? I thought that was the whole idea of >> that setting though? >> >> On Thu, Aug 17, 2017 at 9:52 AM, Carlos Ro

Re: Adding a new node with the double of disk space

No. If you would double all the hardware on that node vs the others would still be a bad idea. Keep the cluster uniform vnodes wise. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo |

Re: Slowness in C* cluster after implementing multiple network interface configuration.

It might be a bug. Cassandra, AFAIK, scans those files for changes and updates the topology (So you don't need a restart if you change the files). It might be the case that the absence of the file, is still noticed by Cassandra even if it is not really used. I can do a small test to confirm, if

Re: Reaper v0.6.1 released

Great! Thanks a lot! Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin: *linkedin.com/in/carlosjuzarterolo * Mobile:

Re: Cassandra Schema version mismatch

Are you changing the schema in a dynamic fashion? If you get problems (network, gc pauses, etc) during the schema changes it might lead to that. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter:

Re: Cassandra Schema version mismatch

Sometimes "resetlocalschema" (happened to me, didn't check why) will not work, and you need to stop the offending nodes and bring them back one by one.. That solved the issue. In the cases I've seen this happened the clusters in question where either: a) A couple of nodes down (cloud provider

Re: Stable version apache cassandra 3.X /3.0.X

On sync in Jon. Only go 3.0.x if you REALLY need something from there (ex: MV) even then, be carefull. 3.x wait for 3.11.x. 3.10 if you REALLY need something from there right now. Latest 2.2.x or 2.1.x if you are just doing baseline Cassandra and need the stability. Regards, Carlos Juzarte

Re: Self-healing data integrity?

Wouldn't be easier for 1) The CRC to be checked by the sender, and don't send if it doesn't match? 2) And once the stream ends, you could compare the 2 CRCs to see if something got weird during transfer? Also you could implement this in 2 pieces instead of reviewing the streaming architecture

Re: Schema Mismatch Issue in Production

Which version are you running? I got stuck in a similar situation (With a lot more nodes) and the only way to make it good was to stop the whole cluster, start nodes 1 by 1. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your

Re: truncate table in C* 3.11.0

If you waited less than 60s, no warning/error was issued. Do the following: * Check if all nodes are up (truncate fails if not) * Check if you got a snapshot generated (unless you have auto_snapshot disabled) * Check if you have still the sstables in the directories (you shouldn't) If it didn't

Re: Manual repair not showing in the log.

Can you check if you have any validation compaction running in nodetool compactionstats? On 7 Sep 2017 7:56 pm, "Mark Furlong" wrote: I have started a repair and I received the message ‘Starting repair command #1, repairing 25301 ranges for keyspace x

Re: Materialized views stability

I've been dealing with MV extensively, and I second Blake. MVs are not suitable for production. Unless you're ready for the pain (The out of sync is a major pain point), I would not go that way. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP

  1   2   >