Mix and match SASI with standard indexes not allowed?

Scenario (running 3.9, by the way): CREATE TABLE atc_test1.idxtest ( pk text PRIMARY KEY, col1 text, col2 text); CREATE CUSTOM INDEX idx2 ON atc_test1.idxtest (col2) USING 'org.apache.cassandra.index.sasi.SASIIndex'; CREATE INDEX idx1 ON atc_test1.idxtest (col1); Queries: Works:

Re: unsubscribe

That doesn't work. You need to send an email to user-unsubscr...@cassandra.apache.org On Thu, Oct 27, 2016 at 11:22 AM, Anseh Danesharasteh < anseh.dan...@gmail.com> wrote: > unsubscribe > -- *Scott Hirleman* *Head of US Marketing and Sales* www.smartcat.io https://github.com/smartcat-labs

Re: cqlsh fails to connect

It may be possible that you were using the old version of cqlsh? `which cqlsh` on your upgraded nodes might point to the old install path, or a copied version somewhere in your $PATH, perhaps. Doing a fresh install and checking was a good idea, and it does show that using the current version

Re: how to get the size of the particular partition key belonging to an sstable ??

There are actually multiple tickets for different size functions. Examples include computing size of collections, number of rows, and physical sizes server side. I also have a patch to make the warn and info settable at runtime. https://issues.apache.org/jira/browse/CASSANDRA-12661?filter=-1 It

Re: how to get the size of the particular partition key belonging to an sstable ??

See also  https://issues.apache.org/jira/browse/CASSANDRA-12367 From: Justin Cameron Reply-To: "user@cassandra.apache.org" Date: Friday, October 28, 2016 at 12:35 PM To: "user@cassandra.apache.org" Subject:

Re: how to get the size of the particular partition key belonging to an sstable ??

nodetool cfhistograms / nodetool tablehistograms will also output partition size statistics for a given table: http://docs.datastax.com/en/cassandra/3.0/cassandra/tools/toolsTablehisto.html On Fri, 28 Oct 2016 at 12:32 Justin Cameron wrote: > If you're trying to

Re: how to get the size of the particular partition key belonging to an sstable ??

If you're trying to determine this in order to diagnose wide row issues, then you can check your logs - Cassandra will log a warning for partitions > 100MB during compaction. See

Re: cqlsh fails to connect

Ok, I tried with a new empty one node cluster of the same DSE version and cqlsh works without hiccups. So, the whole issue exists because I upgraded from Cassandra 2.1.11. The procedure I followed for the upgrade was very simple: - nodetool drain (on all nodes) - shutdown all nodes - Uncompressed

Re: Tools to manage repairs

Vincent: currently big partitions, even if you're using paging & slicing by clustering keys, will give you performance problems over time. Please read the JIRAs that Alex linked to, they provide in depth explanations as to why, from some of the best Cassandra operators in the world :) On Fri,

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Haven't seen this before, but perhaps it's related to CASSANDRA-10433? This is just a wild guess as it's in a related codepath, but maybe worth trying out the patch available to see if it helps anything... 2016-10-28 15:03 GMT-02:00 Dikang Gu : > We are seeing huge cpu

Upgrade from 3.6 to 3.9

Hi, Anyone been updated Cassandra to version 3.9 on live system? I've updated our two DC's Cassandra cluster from 3.6 to 3.9 and on the new nodes I experienced relative huge CPU and memory footprint during the handshake with the old nodes (sometimes run out of memory: OutOfMemoryError: Java heap

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

We are seeing huge cpu regression when upgrading one of our 2.0.16 cluster to 2.1.14 as well. The 2.1.14 node is not able to handle the same amount of read traffic as the 2.0.16 node, actually, it's less than 50%. And in the perf results, the first line could go as high as 50%, as we turn up the

Re: Tools to manage repairs

Well I only asked that because I wanted to make sure that we're not doing it wrong, because that's actually how we query stuff, we always provide a cluster key or a range of cluster keys. But yes, I understand that compactions may suffer and/or there may be hidden bottlenecks because of big

Re: cqlsh fails to connect

Hi Rajesh, I just tried python 2.711 & 2.7.12 and I get the same error 'invalid continuation byte'. On Fri, Oct 28, 2016 at 11:53 AM, Rajesh Radhakrishnan < rajesh.radhakrish...@phe.gov.uk> wrote: > > Hi John Z, > > Did you tried running with latest Python 2.7.11 or 2.7.12? > > Kind regards, >

Re: Tools to manage repairs

On Fri, Oct 28, 2016 at 11:21 AM, Vincent Rischmann wrote: > Doesn't paging help with this ? Also if we select a range via the cluster > key we're never really selecting the full partition. Or is that wrong ? > > > On Fri, Oct 28, 2016, at 05:00 PM, Edward Capriolo wrote: > >

RE: cqlsh fails to connect

Hi John Z, Did you tried running with latest Python 2.7.11 or 2.7.12? Kind regards, Rajesh Radhakrishnan From: Ioannis Zafiropoulos [john...@gmail.com] Sent: 27 October 2016 22:16 To: user@cassandra.apache.org Subject: cqlsh fails to connect I upgraded DSE

Re: Tools to manage repairs

Doesn't paging help with this ? Also if we select a range via the cluster key we're never really selecting the full partition. Or is that wrong ? On Fri, Oct 28, 2016, at 05:00 PM, Edward Capriolo wrote: > Big partitions are an anti-pattern here is why: > > First Cassandra is not an analytic

Re: Tools to manage repairs

Big partitions are an anti-pattern here is why: First Cassandra is not an analytic datastore. Sure it has some UDFs and aggregate UDFs, but the true purpose of the data store is to satisfy point reads. Operations have strict timeouts: # How long the coordinator should wait for read operations to

Re: Tools to manage repairs

Hi Eric, that would be https://issues.apache.org/jira/browse/CASSANDRA-9754 by Michael Kjellman and https://issues.apache.org/jira/browse/CASSANDRA-11206 by Robert Stupp. If you haven't seen it yet, Robert's summit talk on big partitions is totally worth it : Video :

Re: Tools to manage repairs

On Thu, Oct 27, 2016 at 4:13 PM, Alexander Dejanovski wrote: > A few patches are pushing the limits of partition sizes so we may soon be > more comfortable with big partitions. You don't happen to have Jira links to these handy, do you? -- Eric Evans

Re: Cassandra failure during read query at consistency QUORUM (2 responses were required but only 0 replica responded, 2 failed)

This looks like another case of an assert bubbling through try catch that don't catch assert On Fri, Oct 28, 2016 at 6:30 AM, Denis Mikhaylov wrote: > Hi! > > We’re running Cassandra 3.9 > > On the application side I see failed reads with this exception >

Cassandra failure during read query at consistency QUORUM (2 responses were required but only 0 replica responded, 2 failed)

Hi! We’re running Cassandra 3.9 On the application side I see failed reads with this exception com.datastax.driver.core.exceptions.ReadFailureException: Cassandra failure during read query at consistency QUORUM (2 responses were required but only 0 replica responded, 2 failed) On the server

Re: How does the "batch" commit log sync works

That is the maximum length of time that queries may be batched together for, not the minimum. If there is a break in the flow of queries for the commit log, it will commit those outstanding immediately. It will anyway commit in clusters of commit log file size (default 32Mb). I know the

Re: Property file snitch and unbalanced cluster

Hi Robert, What has happened is that you have now two datacenters in your cluster. The way they replicate information will depend on your keyspace settings. Regarding your process I don't think it is safe to do it that way. I'd start off by decommissioning nodes 4 and 5 so that your cluster is

Re: how to get the size of the particular partition key belonging to an sstable ??

Hi, I guess it's about getting particular Partition Size on disk. If so, I would like to know this too. 2016-10-28 9:09 GMT+03:00 Vladimir Yudovin : > Hi, > > >size of a particular partition key > Can you please elucidate this? Key can be just number, or string, or >

Property file snitch and unbalanced cluster

Hi guys, I have a cluster with 5 nodes, cassandra 3.0.5, RF=2, PropertyFileSnitch. Three of the nodes were added initially, DC=PRD. The other two were added more recently. The default for unknown nodes default=DC1:r1 (which is bad in my case, as it would have been nice to have PRD as default)

Unsubscribe

Unsubscribe Regards, Kunal Gaikwad

Re: how to get the size of the particular partition key belonging to an sstable ??

Hi, size of a particular partition key Can you please elucidate this? Key can be just number, or string, or several values. Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Thu, 27 Oct 2016 11:45:47 -0400Pranay akula

Re: Re : Generic keystore when enabling SSL

Hi Jacob, there is no problem to use the same certificate (whether issued by some authority or self signed) on all nodes until it's present in truststore. CN doesn't matter in this case, it can be any string you want. Would this impact client-to-node encryption Nu, but clients should