Re: Cassandra 4.0 upgrade - Upgradesstables

distant future. > > – Scott > > On Aug 16, 2022, at 6:32 AM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > > > Thank you Erick, > > > it is going to be single-threaded by default so it will take a while to > get through all the sstables on

Re: Question about num_tokens

uster takes less than half as long to > complete repairs via Reaper. It also spends more time on GC, though I > can't tell whether that's due to vnodes or other differences. > > On Sun, Mar 13, 2022 at 5:59 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > &

Re: Cassandra 4.0 upgrade - Upgradesstables

Thank you Erick, > it is going to be single-threaded by default so it will take a while to get through all the sstables on dense nodes Is there any downside if the upgradesstables take longer (example 1-2 days), other than I/O? Also when is the upgradesstable get triggered? after every node is

Cassandra 4.0 upgrade - Upgradesstables

Hello, I am evaluating the upgrade from 3.11.x to 4.0.x and as per CASSANDRA-14197 we don't need to run upgradesstables any more. We have tested this in a test environment and see that setting "-Dcassandra.automatic_sstable_upgrade=true"

Re: Datastax Java Driver Compatibility Matrix

ump your dependency version and immediately pick up a large > number of bugfixes. > > But yes, Java Driver 3.2 will work fine using CQLv4 or CQLv3 with > Cassandra 4.0. > > – Scott > > On Apr 19, 2022, at 11:45 AM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.c

Re: Datastax Java Driver Compatibility Matrix

vers.html > > The documents say it's partially compatible, what does this mean? What > will be broken if I continue to use 3.0+ driver with Cassandra 4.0? I did a > quick test with my application using 3.2 driver with Cassandra 4.0.3 and it > works fine. > > > On Mon, Apr 19, 2021 at

Re: Datastax Java Driver Compatibility Matrix

? I did a quick test with my application using 3.2 driver with Cassandra 4.0.3 and it works fine. On Mon, Apr 19, 2021 at 7:14 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thank you > > On Monday, April 19, 2021, Erick Ramirez > wrote: > >> Is t

Question about num_tokens

Hello Team, I am currently using num_tokens: 256 (default in 3.11.X version) for my clusters and trying to understand the advantages vs disadvantages of changing it to 16 (I believe 16 is the new recommended value). As per the cassandra documentation

Re: Cassandra 4.0 GA

Thank you for the information On Wed, May 26, 2021 at 5:40 PM Kane Wilson wrote: > On Tue, May 25, 2021 at 6:36 AM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Hello All, >> >> I see that Cassandra 4.0 RC1 is released in April, is there

Cassandra 4.0 GA

Hello All, I see that Cassandra 4.0 RC1 is released in April, is there going to be an official 4.0 GA release or is RC1 considered as an official GA release with Production use? If not is there a tentative timeline for the GA release?

Re: Suggestions on Running UpgradeSSTables

T work depending on which version > you add and which version the losing replicas are running. > > > > On May 19, 2021, at 10:13 PM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >  > Thanks for the suggestions. > > Few more questions on the mix

Re: Suggestions on Running UpgradeSSTables

t; wrote: > >  > How about option 1? Any issues with option 1? > > On Wed, May 19, 2021, 6:58 PM Kane Wilson wrote: > >> On Thu, May 20, 2021 at 11:17 AM Jai Bheemsen Rao Dhanwada < >> jaibheem...@gmail.com> wrote: >> >>> Thanks for the response,

Re: Suggestions on Running UpgradeSSTables

> On May 19, 2021, at 5:15 PM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > > > >  > > Hello, > > > > I am trying to get some suggestions on running upgradesstables(for a > major version upgrade where there is a SSTable format change).

Suggestions on Running UpgradeSSTables

Hello, I am trying to get some suggestions on running upgradesstables(for a major version upgrade where there is a SSTable format change). The Cassandra cluster is set up in 3 datacenters with 18 nodes in each region and here are the 3 options that I am evaluating. 1. Run "nodetool

Re: Question about the num_tokens

Thank you, Is there a specific reason why Cassandra4.0 recommends to use 16 tokens? On Tue, Apr 27, 2021 at 11:11 PM Jeff Jirsa wrote: > > > On Apr 27, 2021, at 10:47 PM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >  > Hello, > > I am curr

Question about the num_tokens

Hello, I am currently using num_tokens: 256 in my cluster with the version 3.11.6 and when I looked at the Cassandra4.0 I see the num_tokens set to 16. Is there a specific reason for changing the default value from 256 to 16? What is the best value to use ? If 16 is recommended, is there a way

Re: Datastax Java Driver Compatibility Matrix

Thank you On Monday, April 19, 2021, Erick Ramirez wrote: > Is there a Datastax Java Driver >> >> Compatibility matrix available for Cassandra 4.0? >> > > No, there isn't but the same driver versions apply to C* 4.0

Datastax Java Driver Compatibility Matrix

Hello, Is there a Datastax Java Driver Compatibility matrix available for Cassandra 4.0?

Re: Memory Map settings for Cassandra

on as you won't be making full use of your available memory. > > raft.so - Cassandra consulting, support, and managed services > > > On Fri, Apr 16, 2021 at 10:10 AM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Also, >> >> I just

Re: Memory Map settings for Cassandra

m > number of memory map areas per process (vm.max_map_count) 65530 is too low, > recommended value: 1048575, you can change it with sysctl. On Thu, Apr 15, 2021 at 4:45 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thank you Kane and Jeff. > > can I survive

Re: Memory Map settings for Cassandra

y to up your limits as the first >> course of action. >> >> raft.so - Cassandra consulting, support, and managed services >> >> >> On Fri, Apr 16, 2021 at 4:29 AM Jai Bheemsen Rao Dhanwada < >> jaibheem...@gmail.com> wrote: >> >>> Hello A

Memory Map settings for Cassandra

Hello All, The recommended settings for Cassandra suggests to have a higher value for vm.max_map_count than the default 65530 WARN [main] 2021-04-14 19:10:52,528 StartupChecks.java:311 - Maximum > number of memory map areas per process (vm.max_map_count) 65530 is too low > , recommended value:

Re: Understanding logging in Cassandra

Thank you all, Kane: Is there a list of logger names available for each task like compaction, memtable flush etc? Paulo: I have a cluster with a very high number of tables, yes just during the boot-up time, I see a very huge number of logs in the range > 100Mb. So I am trying to tune the logging

Understanding logging in Cassandra

Hello, I recently moved from C* version 2.1.16 to 3.11.6 and I see a lot of difference in logging between these two versions. Can someone please help me with the below questions? - Default log level in 2.1.16 is INFO

Re: Increased read latency with Cassandra >= 3.11.7

Any update on this? Any idea if this is already tracked under JIRA issue, so we can follow for updates On Wednesday, February 10, 2021, Johannes Weißl wrote: > Hi Nico, > > On Mon, Sep 14, 2020 at 03:51PM +0200, Nicolai Lune Vest wrote: > > after upgrading my Cassandra nodes from version 3.11.6

Re: SSTableloader questions

n(Thread.java:748) ~[na:1.8.0_272] > progress: total: 100% 0.000KiB/s (avg: 0.000KiB/s) On Mon, Nov 9, 2020 at 3:08 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks Erick, I will go through the posts and get back if I have any > questions. >

Re: SSTableloader questions

Thanks Erick, I will go through the posts and get back if I have any questions. On Mon, Nov 9, 2020 at 1:58 PM Erick Ramirez wrote: > A few months ago, I was asked a similar question so I wrote instructions > for this. It depends on whether the clusters are identical or not. The > posts define

SSTableloader questions

Hello, I have few questions regarding restoring the data from snapshots using sstableloader. If i have a 6 node cassandra cluster with VNODEs(256) and I have taken snapshot of all 6 nodes and if I have to restore to another cluster 1. Does the target cluster have to be of the same size? 2. If 1

Increased read latency with Cassandra >= 3.11.7

Hello Nicolai, I am also looking to upgrade to 3.11.8. Is the latency you noticed is only with TWCS? And others looks good? On Thursday, November 5, 2020, Ahmed Eljami wrote: > +1 > I would also be interested to know if the 3.11.9 provide any improvement > for your case. > Cheers. > > Le mer.

Re: Repeated messages about Removing tokens

Yes correct, for the same node the log message is repeating On Monday, October 5, 2020, Erick Ramirez wrote: > Yes, This log entry is expected during the decommission and happens only >> once. But in my case I see these messages repeating several 1000 times a >> day and continuing. Even the

Re: Repeated messages about Removing tokens

Yes, This log entry is expected during the decommission and happens only once. But in my case I see these messages repeating several 1000 times a day and continuing. Even the restart of C* process didn't work. On Sun, Oct 4, 2020 at 11:49 PM Erick Ramirez wrote: > yes correct, I gracefully

Re: Repeated messages about Removing tokens

yes correct, I gracefully decommissioned a few nodes from the cluster and I see the below log messages for all the decommissioned servers. INFO [GossipStage:51] 2020-10-05 05:54:10,429 Gossiper.java:1010 - > InetAddress /x.x.x.x is now DOWN > INFO [GossipStage:51] 2020-10-05 05:54:10,430

Re: Repeated messages about Removing tokens

Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > No, I always performed addition and decommission one node at a time. > > On Wed, Aug 26, 2020 at 5:42 AM Hossein Ghiyasi Mehr < > ghiyasim...@gmail.com> wrote: > >> Is it possible to remove/decommissio

Re: Understanding replication

y key, then they will be resolved via > data timestamp. > > On Sun, Sep 20, 2020 at 5:31 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Hello, >> >> I have a question regarding multi Datacenter replication. >> In a multi datacen

Understanding replication

Hello, I have a question regarding multi Datacenter replication. In a multi datacenter(dc-1, dc-2) if two records are written into dc-1 is there a guarantee that these two records replicate to dc-2 in the same order or is there a possibility that second insert replicate faster than first insert?

Re: Inter Data Center Latency calculation of a Multi DC cluster running in AWS

Thank you On Fri, Sep 18, 2020 at 4:59 PM Erick Ramirez wrote: > For the metrics >> "org.apache.cassandra.metrics:name=[DC]-Latency,type=Messaging" which is >> the unit of the metrics? >> > > They're in milliseconds: > > timer.update(timeTaken, TimeUnit.MILLISECONDS); >

Re: Inter Data Center Latency calculation of a Multi DC cluster running in AWS

Hello, For the metrics "org.apache.cassandra.metrics:name=[DC]-Latency,type=Messaging" which is the unit of the metrics? -b -i -q 75thPercentile 999thPercentile DurationUnitMax Min StdDev -d

Re: Repeated messages about Removing tokens

ps a bit too verbose if the >> message is being printed more than once per node removal (in which case you >> should probably open a JIRA to fix it). >> >> Em qua., 19 de ago. de 2020 às 02:30, Jai Bheemsen Rao Dhanwada < >> jaibheem...@gmail.com> escreveu: >> &

Re: Repeated messages about Removing tokens

Yes correct i have seen these messages but in one of cluster i see these messages are repeated ~3000 times per day On Tuesday, August 18, 2020, Erick Ramirez wrote: > Yes, it is normal to see that message when you are decommissioning nodes. > It just means that the token ownership(s) is getting

Re: Encrypting JMX password for cassandra

Thank you, I looked at this post but haven't tried. let me give a try On Tue, Aug 18, 2020 at 1:13 AM Johnny Miller wrote: > Jai, > > I haven't tried it myself, but you might be able to implement something > like this as I believe this is generic to Java. > >

Repeated messages about Removing tokens

Hello, I am trying to add and decommission some nodes into the cluster. While some nodes are decommissioned I see the below error messages repeatedly on the rest of C* nodes logs. It's not for all the IPs but for a few of them. Is this an issue? INFO [GossipStage:7] 2020-08-18 04:22:07,168

Re: Encrypting JMX password for cassandra

Thanks Erick Can you please point me the doc for internal c* auth? Are you referring to c* auth for jmx? On Monday, August 17, 2020, Erick Ramirez wrote: > No, there isn't. You can either set the permissions to 400 so only the OS > cassandra user can read the file or enable internal C* auth so

Encrypting JMX password for cassandra

Hello, When enabling JMX Authentication , username and password are stored as plain text in jmxremote.password file. Is there a way to encrypt the content of this file so it's not human readable?

Re: Cqlsh copy command on a larger data set

thank you On Thu, Jul 16, 2020 at 12:29 PM Alex Ott wrote: > look into a series of the blog posts that I sent, I think that it should > be in the 4th post > > On Thu, Jul 16, 2020 at 8:27 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> okay, is

Re: Cqlsh copy command on a larger data set

okay, is there a way to export the TTL using CQLsh or DSBulk? On Thu, Jul 16, 2020 at 11:20 AM Alex Ott wrote: > if you didn't export TTL explicitly, and didn't load it back, then you'll > get not expirable data. > > On Thu, Jul 16, 2020 at 7:48 PM Jai Bheemsen Rao Dhanwada

Re: Cqlsh copy command on a larger data set

58 (2 rows) On Wed, Jul 15, 2020 at 1:17 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > thank you > > On Wed, Jul 15, 2020 at 1:11 PM Russell Spitzer > wrote: > >> Alex is referring to the "writetime" and "tttl" values for each cell. &

Re: Cqlsh copy command on a larger data set

e a new writetime value which > matches the copy time rather than initial insert time. > > On Wed, Jul 15, 2020 at 3:01 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Hello Alex, >> >> >>- use DSBulk - it's a very effective tool for

Re: Cqlsh copy command on a larger data set

you mean by "preserving metadata" ? would you mind explaining? On Tue, Jul 14, 2020 at 8:50 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thank you for the suggestions > > On Tue, Jul 14, 2020 at 1:42 AM Alex Ott wrote: > >> CQLSH definitely won'

Re: Cqlsh copy command on a larger data set

astax.com/blog/2019/07/datastax-bulk-loader-counting >- > > https://www.datastax.com/blog/2019/12/datastax-bulk-loader-examples-loading-other-locations > > > On Tue, Jul 14, 2020 at 1:47 AM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Hel

Cqlsh copy command on a larger data set

Hello, I would like to copy some data from one cassandra cluster to another cassandra cluster using the CQLSH copy command. Is this the good approach if the dataset size on the source cluster is very high(500G - 1TB)? If not what is the safe approach? and are there any limitations/known issues to

Validate data consistency after nodetool rebuild

Hello, I am trying to expand my C* cluster to a new region, followed by keyspace expansion and nodetool rebuild -- sourceDC. Once the rebuild process is complete, is there a way to identify if all the data between two regions is in sync? Since the data size is large, I cannot run select count(*).

Re: Cassandra write path during the decommissioning process

1 (pending), > quorum becomes 3 of 4. > > On Mon, Jun 29, 2020 at 12:48 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Can someone please share thoughts on this? >> >> On Wed, Jun 24, 2020 at 4:25 PM Jai Bheemsen Rao Dhanwada

Re: Cassandra write path during the decommissioning process

Can someone please share thoughts on this? On Wed, Jun 24, 2020 at 4:25 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello, > > I would like to understand how the writes happen when there is a node in > the cluster that is being decommissioned. > >

Cassandra write path during the decommissioning process

Hello, I would like to understand how the writes happen when there is a node in the cluster that is being decommissioned. During the decommission process, the node will send the streams to the rest of the nodes that it owns. what happened to the read and write of the data that is owned by the

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

ansion > first and than upgrade. But finally we upgraded and than expanded. > > As per our experience what I could tell you is, it is not advisable to add > new nodes on higher version. > > There are many bugs which got fixed from 3.11.3 to 3.11.6. > > > > Thanks >

Cassandra upgrade from 3.11.3 -> 3.11.6

Hello, I am trying to upgrade from 3.11.3 to 3.11.6. Can I add new nodes with the 3.11.6 version to the cluster running with 3.11.3? Also, I see the SSTable format changed from mc-* to md-*, does this cause any issues?

Re: Cassandra Bootstrap Sequence

ed $ time nodetool compactionstats > pending tasks: 0 > > real 1m17.559s > user 0m2.340s > sys 0m0.248s On Tue, Jun 2, 2020 at 10:25 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Also during this time, I am losing metrics for all the nodes in the >

Re: Cassandra Bootstrap Sequence

, metrics were lost for all the nodes during the 3 minute period. On Tue, Jun 2, 2020 at 7:55 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thank you, > > Does that mean there is no way to improve this delay? And i have to live > with it since i have more tabl

Re: Cassandra Bootstrap Sequence

t most. What you are seeing is the > carving up of memtables for each of those 3,000. I try to limit my clusters > to roughly 100 tables. > > > > > > Sean Durity > > > > *From:* Jai Bheemsen Rao Dhanwada > *Sent:* Tuesday, June 2, 2020 10:48 AM > *To:* user

Re: Cassandra Bootstrap Sequence

3000 tables On Tuesday, June 2, 2020, Durity, Sean R wrote: > How many total tables in the cluster? > > > > > > Sean Durity > > > > *From:* Jai Bheemsen Rao Dhanwada > *Sent:* Monday, June 1, 2020 8:36 PM > *To:* user@cassandra.apache.org > *Su

Re: Cassandra Bootstrap Sequence

Thanks Erick, I see below tasks are being run mostly. I didn't quite understand what exactly these scheduled tasks are for? Is there a way to reduce the boot-up time or do I have to live with this delay? $ zgrep "CompactionStrategyManager.java:380 - Recreating compaction > strategy" debug.log*

Re: Cassandra Bootstrap Sequence

at 3:22 PM Reid Pinchback wrote: > That gap seems a long time. Have you checked GC logs around the timeframe? > > > > *From: *Jai Bheemsen Rao Dhanwada > *Reply-To: *"user@cassandra.apache.org" > *Date: *Monday, June 1, 2020 at 3:52 PM > *To: *"user@cassan

Cassandra Bootstrap Sequence

Hello Team, When I am bootstrapping/restarting a Cassandra Node, there is a delay between gossip settle and port opening. Can someone please explain me where this delay is configured and can this be changed? I don't see any information in the logs In my case if you see there is a ~3 minutes

Re: Decommissioned nodes are in UNREACHABLE state

any inputs here? On Sat, May 2, 2020 at 12:49 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello Alain, > > Thanks for your suggestions. > > Surprisingly, the node which is in unreachable state, is not present in > any of the system tables. I am wonderin

Re: Decommissioned nodes are in UNREACHABLE state

> ----------- > Alain Rodriguez - al...@thelastpickle.com > France / Spain > > The Last Pickle - Apache Cassandra Consulting > http://www.thelastpickle.com > > Le jeu. 13 juin 2019 à 00:55, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> a éc

Re: Understanding "nodetool netstats" on a multi region cluster

This is not causing any issues and with the restart it goes away. But I would like understand why this is happening only on certain DC but not all DC. I am depending on this output to find whether a node is doing any streams or not. On Fri, Apr 17, 2020 at 2:37 AM Erick Ramirez wrote: > The

Re: Understanding "nodetool netstats" on a multi region cluster

Hello Erick, I can see the bootstrap message "Bootstrap 24359390-4443-11ea-af19-1fbf341b76a0" every time, I spin up a 3rd datacenter. I can confirm that there are no network issues and cluster is not overloaded, as this is the new cluster without any data. 1 and 2 regions don't have any Bootstrap

Re: Understanding "nodetool netstats" on a multi region cluster

I could re-produce this behavior all the times in 3rd datacenter and there is network connectivity issues. Also cluster is not overloaded as this is brand new cluster. On Wednesday, April 15, 2020, Erick Ramirez wrote: > *Bootstrap 24359390-4443-11ea-af19-1fbf341b76a0* >> >> > That bootstrap

Understanding "nodetool netstats" on a multi region cluster

Hello, I have 3 region Cassandra clusters and I am trying to look at the "nodetool netstats" output, I see two different outputs in 1,2 regions vs region 3. There is a Bootstrap message in Region 3 and where are it's not present in Region 1 and Region 2, though all the nodes were bootstrapped.

Re: unconfigured table logtabl

Another suggestion before resetlocalschema. Try rolling restart all the nodes in the cluster and see if it fix the problem. After the restart all the nodes will use the same schema for the table. On Sunday, April 5, 2020, David Ni wrote: > Hi Erick > Thank you very much for your friendly note.

Re: JMX mBean for gossipinfo/status

getEndpointSnitchInfoProxy(). > > In the case of gossipinfo, it's from org.apache.cassandra.net: > type=FailureDetector. > > On Mon, Mar 30, 2020 at 1:55 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Hello All, >> >> I am trying

Re: JMX mBean for gossipinfo/status

I tried looking at the org.apache.cassandra.db:type=StorageService mBean, but don't see an option for the datacenter On Mon, Mar 30, 2020 at 11:55 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello All, > > I am trying to find the mBean that gives information

JMX mBean for gossipinfo/status

Hello All, I am trying to find the mBean that gives information for "node tool gossipinfo" or "nodetool status". Back ground: I am trying find the available Datacenters in my Cassandra cluster using the JMX mBeans. Thanks in advance.

Handling Long running Cassandra Rebuild Process

Hello, When I invoke "node tool rebuild" command, I see it is a long running process depending on the data size. I am implementing an API using the JMX mBeans, since the rebuild is a long running operation, the API is waiting for the rebuild to complete. Is there a way to make it asynchronous and

Re: [EXTERNAL] Re: Cassandra Encyrption between DC

thank you On Thu, Feb 13, 2020 at 6:30 AM Durity, Sean R wrote: > I will just add-on that I usually reserve security changes as the primary > exception where app downtime may be necessary with Cassandra. (DSE has some > Transitional tools that are useful, though.) Sometimes a short outage is >

Cassandra Encyrption between DC

Hello, Is there a way we can have a multi DC Cassandra cluster, where dc-1 have encryption enabled and dc-2 does't have encryption? I am trying to add a new DC to the existing cluster, where existing dc don't have encryption between the nodes but the new DC have encryption enabled? I see the

Re: cassandra-cli on 3.x

thank you On Tue, Feb 11, 2020 at 6:38 PM Erick Ramirez wrote: > I am using astyanax client > > > Right. It was announced as being retired back in 2016 [1] which ended in > 2018 [2]: > > >> >> *DeprecationAstyanax has been retired and is no longer under active >> development but may receive

Re: cassandra-cli on 3.x

I am using astyanax client On Tuesday, February 11, 2020, Erick Ramirez wrote: > Jai, Thrift was deprecated years ago (maybe 5 or 6?) and COMPACT STORAGE > was dropped since the refactor of the storage engine in C* 3.0 so there > won't be support for any legacy CLI. In fact, you need to migrate

cassandra-cli on 3.x

Hello, I have Cassandra cluster(2.1.16) where the application is using the legacy thrift schema (Cassandra-cli). I am planning to upgrade the cluster to 3.11.X without changing the schema. but the new 3.x doesn't have cassandra-cli utilities. is there any alternative to get the cli installed on

Re: Log output when Cassandra is "up"?

One more better way if you would like to do using cli is nodetool statusbinary running: if cql port starts up Not running: if the machine is not ready to accept reads and writes On Monday, January 13, 2020, Erick Ramirez wrote: > Yes, a line like this in the system.log indicates that Cassandra

Recommendations for Tuning BloomFilter values

Hello, I am trying to understand pros and cons of tuning(increasing) the bloom filter value, to optimize the read performance. are there any guidelines on increasing the value. I am using LeveledCompactionStrategy, so the default bloom_filter_fp_chance is 0.1

Re: Cassandra loglevel in 3.11.x version

DEBUG logs to debug.logs, only when I set the loglevel to DEBUG? Here is my logback.xml <https://pastebin.com/UD3hSTtr> Thanks in advance. On Fri, Sep 6, 2019 at 4:01 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > does anyone know if there is a documentation

Re: Cassandra loglevel in 3.11.x version

does anyone know if there is a documentation that lists all the classes for logs? On Fri, Sep 6, 2019 at 9:28 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks Allen, > > This works, is there any documentation that explain about all the > available logging

Re: Cassandra loglevel in 3.11.x version

Thanks Allen, This works, is there any documentation that explain about all the available logging levels? On Fri, Sep 6, 2019 at 12:07 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks, I will try that. > > Is this changed between 2.1.16 to 3.11.3? > > O

Re: Cassandra loglevel in 3.11.x version

andra.transport TRACE > > this will help you see all your queries in logs. > Just beware that this fills up logs really fast. > > Thanks, > Allen > > On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, < > jaibheem...@gmail.com> wrote: > >> Hello, >>

Cassandra loglevel in 3.11.x version

Hello, I am trying to enable debug logs on the Cassandra cluster running with 3.11.3, I do see some debug logs but I don't see the same level of DEBUG logs I used to see with 2.1.16 version of cassandra. I am using the below command to set debug logging. $ nodetool setlogginglevel

Re: [EXTERNAL] Apache Cassandra upgrade path

it might be useless > depending on your procedure.) > > Romain > > > > Le vendredi 26 juillet 2019 à 23:51:52 UTC+2, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> a écrit : > > > yes correct, it doesn't work for the servers. trying to see if any had any

Re: [EXTERNAL] Apache Cassandra upgrade path

ultant > > https://www.instaclustr.com/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.instaclustr.com_=DwMFaQ=MtgQEAMQGqekjTjiAhkudQ=aC_gxC6z_4f9GLlbWiKzHm1vucZTtVYWDDvyLkh8IaQ=JUUAJpaOGj5fhLX2uWOwUVqUcHN3c24hEaDC1T8RZVQ=gQuE9u1lRiSA9uZsshvcKIuYih5Rvz3v6lhUOLZzvw4=>

Re: [EXTERNAL] Apache Cassandra upgrade path

Don’t stay in a mixed state very long. The cluster > will function fine in a mixed state – except for those streaming > operations. No repairs, no bootstraps. > > > > > > Sean Durity – Staff Systems Engineer, Cassandra > > > > *From:* Jai Bheemsen Rao

Apache Cassandra upgrade path

Hello, I am trying to upgrade Apache Cassandra from 2.1.16 to 3.11.3, the regular rolling upgrade process works fine without any issues. However, I am running into an issue where if there is a node with older version dies (hardware failure) and a new node comes up and tries to bootstrap, it's

Decommissioned nodes are in UNREACHABLE state

Hello, I have a Cassandra cluster running with 2.1.16 version of Cassandra, where I have decommissioned few nodes from the cluster using "nodetool decommission", but I see the node IPs in UNREACHABLE state in "nodetool describecluster" output. I believe they appear only for 72 hours, but in my

Re: Disable Truststore CA check for internode_encryption

> > Is server encryption option ”require_client_auth: false” what you are > after? > > > Hannu > > > Jai Bheemsen Rao Dhanwada kirjoitti 28.2.2019 > kello 1.57: > > > Hello, > > > Is it possible

Re: Disable Truststore CA check for internode_encryption

öger wrote: > > > > Is server encryption option ”require_client_auth: false” what you are > after? > > > > Hannu > > > >> Jai Bheemsen Rao Dhanwada kirjoitti 28.2.2019 > kello 1.57: > >> > >> Hello, > >> > >> Is it possi

Re: Disable Truststore CA check for internode_encryption

I am trying to setup 1-way SSL, basically I am trying to use the SSL options only for the encrypt the data on the wire and trust everyone who is connecting to me. On Wed, Feb 27, 2019 at 4:18 PM Kenneth Brotman wrote: > Hello, > > > > Why would you want to do that? > > >

Disable Truststore CA check for internode_encryption

Hello, Is it possible to disable truststore CA check for the cassandra internode_encyrption? if yes, is there a config property to do that?

Re: Datastax Java Driver compatibility

wrote: > Hi there- > > I checked with the team here (at DataStax) and this should work. Any > reason you need to stick with Java Driver 3.2, there is a 3.6 release. > > Thanks! > > Amanda > > On Tue, Jan 22, 2019 at 8:45 AM Jai Bheemsen Rao Dhanwada < > jaib

Datastax Java Driver compatibility

Hello, I am looking for Datastax Driver compatibility vs apache cassandra 3.11.3 version. However the doc doesn't talk about the 3.11 version. https://docs.datastax.com/en/driver-matrix/doc/driver_matrix/javaDrivers.html Can someone please confirm if the Datastax Java Driver 3.2.0 version work

Re: How to measure the schema size

ion-15f868df73ed46488d1d159da20858d4.aspx?r=cc6bf9aa-c933-4d93-9501-904fd550e1ad=mainreglink=true> > > 20% Discount Code: estevez20 > > > On Fri, Oct 26, 2018 at 6:25 PM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> anyone has any idea on

Re: How to measure the schema size

anyone has any idea on this? On Thu, Oct 25, 2018 at 11:35 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello, > > I am running into a situation where huge schema (# of CF) causing OOM > issues to the heap. is there a way to measure how much size each co

How to measure the schema size

Hello, I am running into a situation where huge schema (# of CF) causing OOM issues to the heap. is there a way to measure how much size each column family uses in the heap?

  1   2   >