Re: tablehistogram shows high sstables

2021-04-30 Thread vytenis silgalis
17ms read latency for the 50th percentile is actually a pretty high latency
in my experience, I prefer to see the 75th percentile read latency to be
around 1-2ms.  Of course it depends on your use case and what your
performance objectives are.

On Thu, Apr 29, 2021 at 7:05 AM Kane Wilson  wrote:

> It does imply the SSTables are being read - how big is your data size and
> how much memory on the nodes? It's certainly possible to get low latencies
> despite many SSTables, but I'd expect small read sizes paired with a lot of
> memory.
>
>
> raft.so - Cassandra consulting, support, managed services
>
> On Thu., 29 Apr. 2021, 08:44 Ayub M,  wrote:
>
>> The table has 24 sstables with size tiered compaction, when I run
>> nodetool tablehistograms I see 99% percentile of the queries are showing up
>> 24 as the number of sstables. But the read latency is very low, my
>> understanding from the tableshistograms's sstable column is - it shows how
>> many sstables were read to complete the query. If so reading 24 sstables
>> should take sometime, at least maybe couple of seconds. Am I missing
>> something here? Does checking against index/bloom filters count towards
>> sstable counter as well?
>>
>> Percentile  SSTables Write Latency  Read LatencyPartition Size   
>>  Cell Count
>>   (micros)  (micros)   (bytes)
>> 50%24.00 17.08  17436.92   310   
>>   6
>> 75%24.00 24.60  20924.30   446   
>>   6
>> 95%24.00 42.51  62479.63   770   
>>  10
>> 98%24.00 51.01  74975.55  1597   
>>  17
>> 99%24.00 61.21  74975.55  3311   
>>  24
>> Min18.00  2.30   4866.3287   
>>   0
>> Max24.00943.13  89970.66545791   
>>   17084
>>
>>


RE: Cassandra 3.11 cqlsh doesn't work with latest JDK

2021-04-30 Thread Durity, Sean R
Try adding this into the SSL section of your cqlshrc file:
version = SSLv23


Sean Durity

From: Maxim Parkachov 
Sent: Friday, April 30, 2021 8:57 AM
To: user@cassandra.apache.org; d...@cassandra.apache.org
Subject: [EXTERNAL] Cassandra 3.11 cqlsh doesn't work with latest JDK

Hi everyone,

I have Apache Cassandra 3.11.6 with SSL encryption, CentOS Linux release 7.9, 
python 2.7.5. JDK and python are coming from operating system.

I have updated today operating system and with that I've got new JDK

$ java -version
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (build 25.292-b10, mixed mode)

Now when I try to connect to my local instance of Cassandra with cqlsh I'm 
getting error:

$ cqlsh --ssl -u cassandra -p cassandra
Connection error: ('Unable to connect to any servers', {'127.0.0.1': error(1, 
u"Tried connecting to [('127.0.0.1', 9142)]. Last error: [SSL: 
WRONG_VERSION_NUMBER] wrong version number (_ssl.c:618)")})

Apparently, latest release of JDK *_292 disabled TLS1.0 and TLS1.1.

Is this known issue ? Is there is something I could do to quickly remedy the 
situation ?

Thanks in advance,
Maxim.




The information in this Internet Email is confidential and may be legally 
privileged. It is intended solely for the addressee. Access to this Email by 
anyone else is unauthorized. If you are not the intended recipient, any 
disclosure, copying, distribution or any action taken or omitted to be taken in 
reliance on it, is prohibited and may be unlawful. When addressed to our 
clients any opinions or advice contained in this Email are subject to the terms 
and conditions expressed in any applicable governing The Home Depot terms of 
business or client engagement letter. The Home Depot disclaims all 
responsibility and liability for the accuracy and content of this attachment 
and for any damages or losses arising from any inaccuracies, errors, viruses, 
e.g., worms, trojan horses, etc., or other items of a destructive nature, which 
may be contained in this attachment and shall not be liable for direct, 
indirect, consequential or special damages in connection with this e-mail 
message or its attachment.


Cassandra 3.11 cqlsh doesn't work with latest JDK

2021-04-30 Thread Maxim Parkachov
Hi everyone,

I have Apache Cassandra 3.11.6 with SSL encryption, CentOS Linux release
7.9, python 2.7.5. JDK and python are coming from operating system.

I have updated today operating system and with that I've got new JDK

$ java -version
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (build 25.292-b10, mixed mode)

Now when I try to connect to my local instance of Cassandra with cqlsh I'm
getting error:

$ cqlsh --ssl -u cassandra -p cassandra
Connection error: ('Unable to connect to any servers', {'127.0.0.1':
error(1, u"Tried connecting to [('127.0.0.1', 9142)]. Last error: [SSL:
WRONG_VERSION_NUMBER] wrong version number (_ssl.c:618)")})

Apparently, latest release of JDK *_292 disabled TLS1.0 and TLS1.1.

Is this known issue ? Is there is something I could do to quickly remedy
the situation ?

Thanks in advance,
Maxim.