Re: High IO Util using TimeWindowCompaction

': ' > org.apache.cassandra.io.compress.LZ4Compressor'} > > AND crc_check_chance = 1.0 > > AND dclocal_read_repair_chance = 0.0 > > AND default_time_to_live = 0 > > AND gc_grace_seconds = 3600 > > AND max_index_interval = 2048 > > AND memtable_flush_period_in_ms = 0 > > AND min_index_interval = 128 > > AND read_repair_chance = 0.0 > > AND speculative_retry = 'NONE'; > > > Thanks, > Kurt > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: DC aware failover

gt; project or do you know other projects that provide same kind of > functionality. > > Thanks... > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: DC aware failover

> Thank you for your help > > > On Nov 16, 2017 10:35 AM, "Alexander Dejanovski" > wrote: > > Hi, > > The policy is used in production at least in my former company. > > I can help if you have issues using it. > > Cheers, > > Le jeu. 16 nov

Re: Huge system.batches table after joining a node (Cassandra 3.11.1)

(100GB) which is about 1/3 of the nodes size. > > Is it safe to truncate the table? > > > > Regards, > > Christian > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Huge system.batches table after joining a node (Cassandra 3.11.1)

Lorenz < christian.lor...@webtrekk.com> wrote: > Hi Alexander, > > > > yes we use MV’s. The size of the batch table is around 10GB on the > existing nodes. Also seems pretty high. > > So is this table (also) used to process MV building? > > > > Regards, >

Re: Huge system.batches table after joining a node (Cassandra 3.11.1)

Just a heads up that (in case you missed it) MVs were retroactively marked as experimental and that a large part of the community considers they should not be used in production. On Thu, Dec 7, 2017 at 4:53 PM Alexander Dejanovski wrote: > Yes, MVs use batches during bootstraps

Re: Deleted data comes back on node decommission

p is required. >> >> Do yo think that extra data which node is not responsible for can lead to >> zombie data? >> >> >> On 13.12.17 18:43, Jeff Jirsa wrote: >> >>> Did you run cleanup before you shrank the cluster? >>> >>> >> -- >> >> Best Regards, >> Python_Max. >> >> >> - >> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: user-h...@cassandra.apache.org >> happen > > > -- > > Best Regards, > Python_Max. > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Full repair caused disk space increase issue

re pare sstable files. I mean they have the same timestamp as > below. I guess one of them or both of them should be deleted after during > repair, but for some unknown reason, the repair process failed to delete > them. > -rw-r--r-- 1 root root 237G Dec 31 12:48 lb-123800-big-Data.db > -rw-r--r-- 1 root root 243G Dec 31 12:48 lb-123801-big-Data.db > > C* version is 2.2.8 with STCS. Any ideas? > > Cheers, > -Simon > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Too many tombstones using TTL

}, >>> { "name" : "c2", "deletion_info" : { "local_delete_time" : >>> "2018-01-10T13:29:25Z" } >>> }, >>> { "name" : "c3", "deletion_info" : { "local_delete_time" : >>> "2018-01-10T13:29:25Z" } >>> } >>> ] >>> } >>> ] >>> } >>> ] >>> >>> The question is why Cassandra creates a tombstone for every column >>> instead of single tombstone per row? >>> >>> In production environment I have a table with ~30 columns and It gives >>> me a warning for 30k tombstones and 300 live rows. It is 30 times more then >>> it could be. >>> Can this behavior be tuned in some way? >>> >>> Thanks. >>> >>> -- >>> Best regards, >>> Python_Max. >>> >> >> > > > -- > Best regards, > Python_Max. > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: vnodes: high availability

Hi, > > > Let's say we have a C* cluster with following parameters: > > - 50 nodes in the cluster > > - RF=3 > > - vnodes=256 per node > > - CL for some queries = QUORUM > > - endpoint_snitch = SimpleSnitch > > > Is it correct that 2 any nodes down will cause unavailability of a > keyrange at CL=QUORUM? > > > Regards, > > Kyrill > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: vnodes: high availability

janv. 2018 à 17:55, Alexander Dejanovski a écrit : > Hi Kyrylo, > > the situation is a bit more nuanced than shown by the Datastax diagram, > which is fairly theoretical. > If you're using SimpleStrategy, there is no rack awareness. Since vnode > distribution is purely random,

Re: Too many tombstones using TTL

here is nothing I can do about it except delete records by key > instead of expiring. > > > On Fri, Jan 12, 2018 at 7:30 PM, Alexander Dejanovski < > a...@thelastpickle.com> wrote: > >> Hi, >> >> As DuyHai said, different TTLs could theoretically be set for diffe

Re: vnodes: high availability

gt; > Kyrill > > > -- > *From:* Alexander Dejanovski > *Sent:* Monday, January 15, 2018 8:14:21 PM > > *To:* user@cassandra.apache.org > *Subject:* Re: vnodes: high availability > > > I was corrected off list that the odds of losing data

Re: TWCS and autocompaction

2-big-Data.db > 12/01/2018 07:59:57 > 28/12/2017 19:08:42 > > My goal is using TWCS for sstables expired fast because lots of new data > is coming in. What is the best approach to archive that? Should I > disable auto compaction? > Thanks in advance. > > > - > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Too many tombstones using TTL

t; as read latency and disk usage are okey? Are tombstones affect repair time > (using reaper)? > > Thanks. > > > On Tue, Jan 16, 2018 at 11:32 AM, Alexander Dejanovski < > a...@thelastpickle.com> wrote: > >> Hi, >> >> could you be more specific about t

Re: New token allocation and adding a new DC

eference to interaction with rebuild: > https://issues.apache.org/jira/browse/CASSANDRA-7032 > Nor do I find any open tickets that would discuss the topic. > > Is it reasonable to open an issue for that or is there some obvious > blocker? > > Thanks, > -- > Alex > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: TWCS and autocompaction

run nodetool compact? > > And for the future crontab nodetool disableautocompaction? > > Thanks > > On 16-01-2018 11:35, Alexander Dejanovski wrote: > > Hi, > > The overlaps you're seeing on time windows aren't due to automatic > compactions, but to read repairs.

Re: New token allocation and adding a new DC

bootstrap=false and only use the automatic > token allocation when we need to scale it out. This seems to be the only > supported way to use it anyway. > > Regards, > -- > Alex > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Alter composite column

alter a column composite. Right now it looks like (int, int, string) but I >> want it to be (int, int, string, string). Is it possible to do this on a >> live cluster without deleting the old data? Can you point me to some >> documentation about this? I can't seem to find

Re: Alter composite column

>>>> ) WITH COMPACT STORAGE >>>> >>>> Is this possible? >>>> Best regards, >>>> Joel >>>> >>>> 2018-01-12 16:53 GMT+01:00 Joel Samuelsson : >>>> >>>>> Hi, >>>>> >>>>> I have an older system (C* 2.1) using Thrift tables on which I want to >>>>> alter a column composite. Right now it looks like (int, int, string) but I >>>>> want it to be (int, int, string, string). Is it possible to do this on a >>>>> live cluster without deleting the old data? Can you point me to some >>>>> documentation about this? I can't seem to find it any more. >>>>> >>>>> Best regards, >>>>> Joel >>>>> >>>> >>>> >>> >> > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: need to reclaim space with TWCS

SSTables with 0.89* droppable tombstones? Or do I (can I?) manually >> delete these files and will c* just ignore the overlapping data and treat >> as tombstoned? >> >> >> >> What else should/could be done? >> >> >> >> Thank you in advance for your advice, >> >> >> >> *__* >> >> *Brian Spindler * >> >> >> >> >> > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: need to reclaim space with TWCS

ing immediately: >>>>> >>>>> >>>>> >>>>> Set *unchecked_tombstone_compaction = true* >>>>> >>>>> Set* tombstone_compaction_interval == TTL + gc_grace_seconds* >>>>> >>>>>

Re: Node won't start

out of the way to > let it start? will it rebuild/refresh size estimates if I remove that > folder? > > thanks > -B > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Medusa : a new OSS backup/restore tool for Apache Cassandra

s, in place restores (same cluster) and remote restores (remote cluster) whether or not the topologies match or not. More details in our latest blog post : https://thelastpickle.com/blog/2019/11/05/cassandra-medusa-backup-tool-is-open-source.html Hope you'll enjoy using it, -

Re: execute is faster than execute_async?

e you an idea on how this can be implemented. Sending hundreds/thousands of queries without waiting for a result will DDoS the cluster, so you should always implement some throttling. Cheers, ----- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consult

Cassandra Reaper 2.0 was released

bsite <http://cassandra-reaper.io/>. Cheers, ----- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: What is "will be anticompacted on range" ?

Hi, Full repair triggers anticompaction as well. Only subrange repair doesn't trigger anticompaction, and in 4.0, AFAIK, full repairs won't involve anticompaction anymore. Cheers, Le lun. 10 févr. 2020 à 19:17, Krish Donald a écrit : > Thanks Jeff, But we are running repair using below command

Re: How to elect a normal node to a seed node

p, so they won't stream data in on their first start. Aside from that, any node can become a seed node at anytime. Just update the seed list on all nodes, roll restart the cluster and you'll have a new set of seed nodes. ----- Alexander Dejanovski France @alexanderdeja Consult

Re: How to predict time to complete for nodetool repair

Also Reaper will skip the anticompaction phase which you might be going through with nodetool (depending on your version of Cassandra). That'll reduce the overall time spent on repair and will remove some compaction pressure. But as Erick said, unless you have past repairs to rely on and a stable

Re: Tool for schema upgrades

I second Alex's recommendation. We use https://github.com/patka/cassandra-migration to manage schema migrations in Reaper and it has a consensus feature to prevent concurrent migrations from clashing. Cheers, Alex Le jeu. 8 oct. 2020 à 19:10, Alex Ott a écrit : > Hi > > Look at https://github.

Re: Anti Compactions while running repair

Hi Manish, Anticompaction is the same whether you run full or incremental repair. Le ven. 6 nov. 2020 à 04:37, manish khandelwal a écrit : > In documentation it is given that while running incremental repairs, anti > compaction is done which results in repaired and unrepaired sstables. Since >

Re: Issue with anti-compaction while running full repair with -pr option

Hi, You have two options to disable anticompaction when running full repair: - add the list of DCs using the --dc flag (even if there's just a single DC in your cluster) - Use subrange repair, which is done by tools such as Reaper (it can be challenging to do it yourself on a vnode cluster). You

Re: Anti Compactions while running repair

gt; Manish > > On Mon, Nov 9, 2020 at 11:17 AM Alexander DEJANOVSKI < > adejanov...@gmail.com> wrote: > >> Hi Manish, >> >> Anticompaction is the same whether you run full or incremental repair. >> >> >> Le ven. 6 nov. 2020 à 04:37, manish khan

Re: Backup cassandra and restore. Best practices

Yes, Minio is supported by Medusa through the S3 compatible backend. I reckon we need to update the docs with a guide on setting up those backends, but it's pretty much the same as ceph s3 rgw in configuring your medusa.ini : - use s3_compatible as storage backend - set the host, port and region se

Re: state of incremental repairs in cassandra 3.x

Hi James, I'd recommend to upgrade to 4.0.1 if you intend to use incremental repair. The changes from CASSANDRA-9143 are massive and couldn't be backported to the 3.11 branch. When moving to incremental, and in order to limit anticompaction o

Re: Switching to Incremental Repair

Hi Sebastian, That's a feature we need to implement in Reaper. I think disallowing the start of the new incremental repair would be easier to manage than pausing the full repair that's already running. It's also what I think I'd expect as a user. I'll create an issue to track this. Le sam. 3 fév

Re: stress testing & lab provisioning tools

Hey Jon, It's awesome to see that you're reviving both these projects! I was eager to get my hands on an updated version of tlp-cluster with up to date AMIs 🎉 tlp-stress is by far the best Cassandra stress tool I've worked with, and I recommend everyone to test easy-cass-stress and build addition

<    1   2