Re: Disk full during new node bootstrap

ve this? > > Run compaction for nodes in that group(to which I'm going to add new node, > as data streams to new nodes from nodes of group to which it is added) > > OR > > Boootstrap/add 2(multiple nodes) at a time? > > > Please suggest better way to fix this. > &

Re: Output of "select token from system.local where key = 'local' "

Hi Siddharth, yes, we are sure token ranges will never overlap (I think the start token in describering output is excluded and the end token included). You can get per host information in the Datastax Java driver using : Set rangesForKeyspace = cluster.getMetadata().getTokenRanges(

Re: Output of "select token from system.local where key = 'local' "

Hi Siddarth, I would recommend running "nodetool describering keyspace_name" as its output is much simpler to reason about : Schema Version:9a091b4e-3712-3149-b187-d2b09250a19b TokenRange: TokenRange(start_token:1943978523300203561, end_token:2137919499801737315, endpoints:[127.0.0.3,

Re: How to start using incremental repairs?

Hi Paulo, don't you think it might be better to keep applying the migration procedure whatever the version ? Anticompaction is pretty expensive on big SSTables and if the cluster has a lot of data, the first run might be very very long if the nodes are dense, and especially with a high number of

Re: race condition for quorum consistency

Hi, the analysis is valid, and strong consistency the Cassandra way means that one client writing at quorum, then reading at quorum will always see his previous write. Two different clients have no guarantee to see the same data when using quorum, as illustrated in your example. Only options

Re: race condition for quorum consistency

B, C respond --> conflict > Because a quorum (2 nodes) responded, the coordinator will return the > latest time stamp and may issue read repair depending on YAML settings. > > So where do you see only one client having this guarantee? > > Regards, > > James > > On

Re: [cassandra 3.6.] Nodetool Repair + tombstone behaviour

There are some suggestions mentioned by *brstgt* which we can try on our > side. > > On Thu, Sep 29, 2016 at 5:42 PM, Atul Saroha <atul.sar...@snapdeal.com> > wrote: > >> Thanks Alexander. >> >> Will look into all these. >> >> On Thu, Sep 29, 2016 at

Re: race condition for quorum consistency

in the foreground before the response is returned to the client. > So, at least from a single client's perspective, you get monotonic reads. > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: New data center to an existing cassandra cluster

Reads at quorum in dc3 will involve dc1 and dc2 as they will require a response from more than half the replicas throughout the Cluster. If you're using RF=3 in each DC, each read will need at least 5 responses, which DC3 cannot provide on its own. You can have troubles if DC3 has more than half

Re: How to start using incremental repairs?

After running some tests I can confirm that using -pr leaves unrepaired SSTables, while removing it shows repaired SSTables only once repair is completed. The purpose of -pr was to lighten the repair process by not repairing ranges RF times, but just once. With incremental repair though, repaired

Re: How to start using incremental repairs?

There are 2 main reasons I see for still having unrepaired sstables after running nodetool repair -pr : 1- new data is still flowing in your database after the repair sessions were launched, and thus hasn't been repaired 2- some repair sessions failed and left unrepaired data on your nodes.

Re: How to get rid of "Cannot start multiple repair sessions over the same sstables" exception

r one there are 31 pending repair. On others there are less > pending repairs (min 12). Is there any recomandation for the restart order? > The one with more less pending repairs first, perhaps? > > Thanks, > Robert > > Robert Sicoie > > On Wed, Sep 28, 2016 at 5:35 PM, Al

Re: [cassandra 3.6.] Nodetool Repair + tombstone behaviour

> > Just want the help how to verify and debug this issue. Help will be > appreciated. > > > -- > Regards, > Atul Saroha > > *Lead Software Engineer | CAMS* > > M: +91 8447784271 > Plot #362, ASF Center - Tower A, 1st Floor, Sec-18, > Udyog Vihar Phase I

Re: [cassandra 3.6.] Nodetool Repair + tombstone behaviour

eady running repair > of same partition on other box for same partition range. We saw error > validation failed with some ip as repair in already running for the same > SSTable. > Just few days back, we had 2 DCs with 3 nodes each and replication was > also 3. It means all data on

Re: WARN Writing large partition for materialized views

; partition... > > for some materialized view. Some have values over 500MB. How this affects > performance? What can/should be done? I suppose is a problem in the schema > design. > > Thanks, > Robert Sicoie > -- - Alexander Dejanovski France @alexand

Re: How to get rid of "Cannot start multiple repair sessions over the same sstables" exception

ngQueue.put(LinkedBlockingQueue.java:339) > ~[na:1.8.0_60]* > * at > org.apache.cassandra.net.OutboundTcpConnection.enqueue(OutboundTcpConnection.java:168) > ~[apache-cassandra-3.0.5.jar:3.0.5]* > * ... 6 common frames omitted* > > > Now if I run nodetool repair I get t

Re: How to get rid of "Cannot start multiple repair sessions over the same sstables" exception

dingCompactions on jmx. > > Is there other way I can find out if is there any anticompaction running > on any node? > > Thanks a lot, > Robert > > Robert Sicoie > > On Wed, Sep 28, 2016 at 4:44 PM, Alexander Dejanovski < > a...@thelastpickle.com> wrote: >

Re: Tools to manage repairs

or more. We were never able to run > one to completion. I'm not sure it's a good idea to disable autocompaction > for that long. > > But maybe I'm wrong. Is it possible to use incremental repairs on some > column family only ? > > > On Thu, Oct 27, 2016, at 05:02 PM, Alexa

Re: Tools to manage repairs

t; less big partitions are around 500Mb and less. > > > On Thu, Oct 27, 2016, at 05:37 PM, Alexander Dejanovski wrote: > > Oh right, that's what they advise :) > I'd say that you should skip the full repair phase in the migration > procedure as that will obviously fail, and just mar

Re: Tools to manage repairs

8, Vincent Rischmann <m...@vrischmann.me> a écrit : > Yeah that particular table is badly designed, I intend to fix it, when the > roadmap allows us to do it :) > What is the recommended maximum partition size ? > > Thanks for all the information. > > > On Thu, Oct 27, 2016,

Re: Can a Select Count(*) Affect Writes in Cassandra?

ived this message in error, please advise the sender > immediately by reply email and delete this message. Thank you. > > > > > > This message may contain confidential and/or privileged information. > If you are not the addressee or authorized to receive this on behalf of > the addressee you must not use, copy, disclose or take action based on this > message or any information herein. > If you have received this message in error, please advise the sender > immediately by reply email and delete this message. Thank you. > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Can a Select Count(*) Affect Writes in Cassandra?

this? > > Thanks! > > > > Shalom Sagges > DBA > T: +972-74-700-4035 <+972%2074-700-4035> > <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> > <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections > > <ht

Re: Can a Select Count(*) Affect Writes in Cassandra?

DBA > T: +972-74-700-4035 > <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> > <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections > > <https://engage.liveperson.com/idc-mobile-first-consumer/?utm_medium=email_source=

Re: problem starting incremental repair using TheLastPicke Reaper

ng the below error. > > > A repair run already exist for the same cluster/keyspace/table but with a > different incremental repair value.Requested value: true | Existing value: > false > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: non incremental repairs with cassandra 2.2+

n 19 October 2016 at 17:13, Alexander Dejanovski <a...@thelastpickle.com> > wrote: > > There aren't that many tools I know to orchestrate repairs and we maintain > a fork of Reaper, that was made by Spotify, and handles incremental repair > : https://github.com/thelastpickle/

Re: problem starting incremental repair using TheLastPicke Reaper

ple.com/in/app/snapdeal-mobile-shopping/id721124909?ls=1=8_source=mobileAppLp_campaign=ios> > [image: > W] > <http://www.windowsphone.com/en-in/store/app/snapdeal/ee17fccf-40d0-4a59-80a3-04da47a5553f> > > On Wed, Oct 19, 2016 at 4:44 PM, Alexander Dejanovski < &

Re: incremental repairs with -pr flag?

law. Global Relay will not be liable for any compliance or > technical information provided herein. All trademarks are the property of > their respective owners. > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: non incremental repairs with cassandra 2.2+

, which should soon be merged to master. Le mer. 19 oct. 2016 19:03, Kant Kodali <k...@peernova.com> a écrit : Also any suggestions on a tool to orchestrate the incremental repair? Like say most commonly used Sent from my iPhone On Oct 19, 2016, at 9:54 AM, Alexander Deja

Re: non incremental repairs with cassandra 2.2+

t; Sent from my iPhone > > On Oct 19, 2016, at 9:54 AM, Alexander Dejanovski <a...@thelastpickle.com> > wrote: > > Hi Kant, > > subrange is a form of full repair, so it will just split the repair > process in smaller yet sequential pieces of work (repair is started

Re: non incremental repairs with cassandra 2.2+

e a way to do full repairs > without continually anti compacting? If we do a full repair on each node > with the -pr flag, will subsequent full repairs also force anti compacting > most (all?) sstables? > > Thanks, > > Sean > -- - Alexander Dejanovski France

Re: non incremental repairs with cassandra 2.2+

the -pr flag, will subsequent full repairs also force anti compacting most (all?) sstables? Thanks, Sean -- ----- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Cassandra 3.6 Repair issue with Reaper

=mobileAppLp_campaign=android> > [image: > A] > <https://itunes.apple.com/in/app/snapdeal-mobile-shopping/id721124909?ls=1=8_source=mobileAppLp_campaign=ios> > [image: > W] > <http://www.windowsphone.com/en-in/store/app/snapdeal/ee17fccf-40d0-4a59-80a3-04da4

Re: Out of memory and/or OOM kill on a cluster

13854232 > Maximum tombstones per slice (last five minutes): 22602.0 > > - regarding swap, it's not disabled anywhere, I must say we never really > thought about it. Does it provide a significant benefit ? > > Thanks for your help, really appreciated ! > > On Mon, Nov 21, 20

Re: repair -pr in crontab

inish times of repairs, and if the runs were > successful? Does the "nodetool repair" command is guaranteed to exit > only after the repair is finished and does it return a status code to a > shell? > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Cassandra reaper

t; Thanks again for the help > > > On Tue, Nov 1, 2016 at 12:26 PM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > > ok thank you, > I will try and update you. > > On Tue, Nov 1, 2016 at 10:57 AM, Alexander Dejanovski < > a...@thelastpickle.com&g

Re: Out of memory and/or OOM kill on a cluster

mission > control but it didn't really help; it's possible I missed it because I have > no idea what to look for exactly. > > Anyone have some advice for troubleshooting this ? > > Thanks. > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Out of memory and/or OOM kill on a cluster

is around 4.6MB, 98% around 2MB. Could the 1% here really have that much impact ? We do write a lot to the biggest table and read quite often too, however I have no way to know if that big partition is ever read. On Mon, Nov 21, 2016, at 01:09 PM, Alexander Dejanovski wrote: Hi Vincent, one of

Re: Cassandra reaper

r > cassandra-reaper.yaml > 3. ./bin/spreaper repair production users > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Cassandra reaper

logs > > On Tue, Nov 1, 2016 at 10:25 AM, Alexander Dejanovski < > a...@thelastpickle.com> wrote: > > Do you have anything in the reaper logs that would show a failure of some > sort ? > Also, can you tell me which version of Cassandra you're using ? > > Thanks >

Re: Cassandra reaper

sity": 0.900, > "keyspace_name": "users", > * "last_event": "no events",* > "owner": "root", > "pause_time": null, > "repair_parallelism": "DATACENTER_AWARE", > "seg

Re: Tools to manage repairs

ervice but I'm wondering how do other Cassandra users manage repairs ? Vincent. -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Tools to manage repairs

?v=N3mGxgnUiRY Slides : http://www.slideshare.net/DataStax/myths-of-big-partitions-robert-stupp-datastax-cassandra-summit-2016 Cheers, On Fri, Oct 28, 2016 at 4:09 PM Eric Evans <john.eric.ev...@gmail.com> wrote: > On Thu, Oct 27, 2016 at 4:13 PM, Alexander Dejanovski > <a...@th

Re: Exception thrown on repair after change was made to existing cassandra type

adPoolExecutor.java:1142) > ~[na:1.8.0_60]* > * at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_60]* > * at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]* > > On the node /x.x.x.y > > Do you any suggestion? > Thank you in advance, > Robert > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Reaper repair seems to "hang"

: 0.9 > * Incremental: true > > Don't want to swamp you with more details or unnecessary logs, especially > as I'd have to sanitize them before sending them out, so please let me know > if there is anything else I can provide, and I'll do my best to get it to > you. > > ​K

Re: Why compacting process uses more data that is expected

a. > > > Hello, > > I believe that output of compactionstats shows you the size of > *uncompressed* data. Can you check (with nodetool tablestats) your > compression ratio? > > -- > Alex > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Reaper repair seems to "hang"

l.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > Hope it helps! > > Regards, > Bhuvan > > According to > https://medium.com/@mlowicki/cassandra-reaper-introduction-ed73410492bf#.f0erygqpk > : > > Segment runner has protection mechanism

Re: Help with data modelling (from MySQL to Cassandra)

A, even if we are > querying by Primary keys, the second query will have 100k+ primary key id’s > in the WHERE clause, and the second solution looks like an anti pattern in > cassandra. > > Could anyone give any advice how would we create a model for our use case? > > Thank you in advance, > Zoltan. > > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: How can I scale my read rate?

that case, with RF= 4 instead of 3, with several clients accessing keys > same key ranges, a coordinator could pick up one node to handle the request > in 4 replicas instead of picking up one node in 3 , thus having > more "workers" to handle a request ? > > Am I wrong here ? > > Thank you for the clarification > > > -- > best, > Alain > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: cassandra OOM

t; # By default, ConcGCThreads is 1/4 of ParallelGCThreads. > > # Setting both to the same value can reduce STW durations. > > #-XX:ConcGCThreads=16 > > > > ### GC logging options -- uncomment to enable > > > > #-XX:+PrintGCDetails > > #-XX:+PrintGCDateStamps > > #-X

Re: cassandra OOM

the sender immediately, delete it from your system and > destroy any copies. You may not further disclose or distribute this email > or its attachments. > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: AWS Cassandra backup/Restore tools

/www.linkedin.com/in/srinivm/> [image: > facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] > <https://twitter.com/mani_srini> [image: g+.png] > <https://plus.google.com/+Datastax/about> > <http://feeds.feedburner.com/datastax> > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

ext, >> > primary key((a,b), c) >> > ); >> > >> > Now I can do select * from hello where a='foo' allow filtering;// This >> works in 3.10 but I wonder if this query results in table scan and if so is >> there any way to limit such that I get max b? >> > >> > Thanks! >> >> > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Regular dropped READ messages

we process each > user update: > - SELECT from a "master" slug to get the fields we need > - from that, compute a list of slugs the user had and a list of slugs > the user should have (for example if he changes timezone we have to update > the slug) > - delete the user fr

Re: manual deletes with TWCS

>> How problematic is it to perform deletes when using TWCS? I am currently >> using TWCS and have some new use cases for performing deletes. So far I >> have avoided performing deletes, but I am wondering what issues I might run >> into. >> >> >> - John >> >> >> > > > -- > > - John > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Regular dropped READ messages

almost always correspond to times > where our schedules SELECTs are happening. That narrows the scope a little, > but still. > > Anyway, I'd appreciate any information about troubleshooting this scenario. > Thanks. > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Multi-node repair fails after upgrading to 3.0.14

356976885], > (-1193448110686154165,-1161640137086921883], > (-3356304907368646189,-3346460884208327912], > (3466596314109623830,346814432669172], > (-9050241313548454460,-9005441616028750657], > (402227699082311580,407458511300218383]]] Validation failed in /FAKE.33.64 > >

Re: Multi-node repair fails after upgrading to 3.0.14

air.ValidationTask.treesReceived(ValidationTask.java:68) > ~[apache-cassandra-3.0.14.jar:3.0.14] > > at > org.apache.cassandra.repair.RepairSession.validationComplete(RepairSession.java:178) > ~[apache-cassandra-3.0.14.jar:3.0.14] > > at > org.apache.cas

Re: Multi-node repair fails after upgrading to 3.0.14

> 2017-09-18 07:59:17 repair finished > > > > > > If running the above nodetool call sequentially on all nodes, repair > finishes without printing a stack trace. > > > > The error message and stack trace isn’t really useful here. Any further > ideas/experiences? &g

Re: GC/CPU increase after upgrading to 3.0.14 (from 2.1.18)

lt;https://maps.google.com/?q=4040+Linz,+Austria,+Freist%C3%A4dterstra%C3%9Fe+313=gmail=g> >> >> The contents of this e-mail are intended for the named addressee only. It >> contains information that may be confidential. Unless you are the named >> addressee or an authorized designee, you may not copy or use it, or >> disclose it to anyone else. If you received it in error please notify us >> immediately and then destroy it. Dynatrace Austria GmbH (registration >> number FN 91482h) is a company registered in Linz whose registered office >> is at 4040 Linz, Austria, Freistädterstraße 313 >> <https://maps.google.com/?q=4040+Linz,+Austria,+Freist%C3%A4dterstra%C3%9Fe+313=gmail=g> >> The contents of this e-mail are intended for the named addressee only. It >> contains information that may be confidential. Unless you are the named >> addressee or an authorized designee, you may not copy or use it, or >> disclose it to anyone else. If you received it in error please notify us >> immediately and then destroy it. Dynatrace Austria GmbH (registration >> number FN 91482h) is a company registered in Linz whose registered office >> is at 4040 Linz, Austria, Freistädterstraße 313 >> <https://maps.google.com/?q=4040+Linz,+Austria,+Freist%C3%A4dterstra%C3%9Fe+313=gmail=g> >> > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Deleted data comes back on node decommission

;> 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: DC aware failover

ing I want to test it. > > Thank you for your help > > > On Nov 16, 2017 10:35 AM, "Alexander Dejanovski" <a...@thelastpickle.com> > wrote: > > Hi, > > The policy is used in production at least in my former company. > > I can help if you have is

Re: STCS leaving sstables behind

fixed nodetool status from > reporting a wrong Load (nearly 2TB per node instead à 300Gb) => we are > loading some data for a week now, it seems that this can happen sometimes > > If anyone ever experienced that kind of behavior I'd be glad to know > whether it is OK or not, I'd like to avoid manually triggering JMX > UserDefinedCompaction ;) > > Thank you > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: DC aware failover

you know about this > 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: High IO Util using TimeWindowCompaction

fault_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: 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)

(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)

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 <a...@thelastpickle.com> wrote: > Yes, MVs use batch

Re: Question About Reaper

>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> We have a cluster with 144 nodes( 3 datacenter) with 256 Vnodes . >>>>>> When we tried to start repairs from opscenter then it showed >>>>>> 1.9Million ranges to repair . >>>>>> And even after doing compaction and strekamthroughput to 0 , >>>>>> opscenter is not able to help us much to finish repair in 9 days >>>>>> timeframe . >>>>>> >>>>>> What is your thought on Reaper ? >>>>>> Do you think , Reaper might be able to help us in this scenario ? >>>>>> >>>>>> Thanks >>>>>> Surbhi >>>>>> >>>>>> >>>>>> -- >>>> Jon Haddad >>>> http://www.rustyrazorblade.com >>>> twitter: rustyrazorblade >>>> >>>> >>>> >>> >>> -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Question About Reaper

; We need to finish repair soon. > > On Mon, May 21, 2018 at 10:53 AM Alexander Dejanovski < > a...@thelastpickle.com> wrote: > >> Hi Subri, >> >> Reaper might indeed be your best chance to reduce the overhead of vnodes >> there. >> The latest

Re: Compaction throughput vs. number of compaction threads?

copy or use it, or > disclose it to anyone else. If you received it in error please notify us > immediately and then destroy it. Dynatrace Austria GmbH (registration > number FN 91482h) is a company registered in Linz whose registered office > is at 4040 Linz, Austria, Freistädterstraße 313 > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Not marking node down due to local pause

> I am seeing some but not a whole lot of dropped mutations. nodetool > tpstats looks ok. > > The growing number of SSTables really makes me think this is an I/O issue. > Casssandra is running in a kubernetes cluster using a SAN which is another > reason I suspect I/O. > >

Re: Full repair caused disk space increase issue

d 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: vnodes: high availability

uster 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: New token allocation and adding a new DC

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: vnodes: high availability

. 2018 à 17:55, Alexander Dejanovski <a...@thelastpickle.com> 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 > distr

Re: vnodes: high availability

s getting worse with increase of > vnodes_per_node/Nnode ratio. > > Please, correct me if I'm wrong. > > > How would the situation differ from this example by DataStax, if we had a > real-life 6-nodes cluster with 8 vnodes on each node? > > > Regards, > > Kyrill > > &

Re: TWCS and autocompaction

; > > --------- > 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

ing 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 different >

Re: Too many tombstones using TTL

on > 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

Re: New token allocation and adding a new DC

ebuild: > 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

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. > You must be reading at quorum or local_quorum which can

Re: need to reclaim space with TWCS

> Hi Alexander, Thanks for your response! I'll give it a shot. >> >> On Sat, Jan 20, 2018 at 10:22 AM Alexander Dejanovski < >> a...@thelastpickle.com> wrote: >> >>> Hi Brian, >>> >>> You should definitely set unchecked_tombstone_compac

Re: need to reclaim space with TWCS

an I expect TWCS/C* to reclaim the space from those >> 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 d

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: Node won't start

Should I move this sstable 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

Re: Incremental repair

repair by -pr option only. > > Question:Is incremental repair is the default repair for cassandra 3.11.2 > version. > > Thanks, > Prachi > > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: URGENT: disable reads from node

plication should be changed for this. > > > On Wednesday, August 29, 2018 2:41 PM, kurt greaves > wrote: > > > Note that you'll miss incoming writes if you do that, so you'll be > inconsistent even after the repair. I'd say best to just query at QUORUM > until you can finish repairs. > &g

Re: URGENT: disable reads from node

t problem we were forced to delete commit logs from > one of nodes. > > Now repair is running, but meanwhile some reads bring no data (RF=2) > > Can this node be excluded from reads queries? And that all reads will be > redirected to other node in the ring? > > > Thank

Re: High IO and poor read performance on 3.11.2 cassandra cluster

ts -H ks.xyz <http://ks.xyz>;* >> Total number of tables: 89 >> >> Keyspace : ks >> Read Count: 1439722 >> Read Latency: 1.8982509581710914 ms >> Write Count: 4222811 >> Write Latency: 0.016324778684151386 ms >> Pending Flushes: 0 >> Table: xyz >> SSTable count: 1036 >> SSTables in each level: [1, 10, 116/100, 909, 0, 0, 0, 0, >> 0] >> Space used (live): 187.09 GiB >> Space used (total): 187.09 GiB >> Space used by snapshots (total): 0 bytes >> Off heap memory used (total): 783.93 MiB >> SSTable Compression Ratio: 0.3238726404414842 >> Number of partitions (estimate): 447095605 >> Memtable cell count: 306194 >> Memtable data size: 20.59 MiB >> Memtable off heap memory used: 0 bytes >> Memtable switch count: 7 >> Local read count: 1440322 >> Local read latency: 6.785 ms >> Local write count: 1408204 >> Local write latency: 0.021 ms >> Pending flushes: 0 >> Percent repaired: 0.0 >> Bloom filter false positives: 19 >> Bloom filter false ratio: 0.3 >> Bloom filter space used: 418.2 MiB >> Bloom filter off heap memory used: 418.19 MiB >> Index summary off heap memory used: 307.75 MiB >> Compression metadata off heap memory used: 57.99 MiB >> Compacted partition minimum bytes: 150 >> Compacted partition maximum bytes: 1916 >> Compacted partition mean bytes: 1003 >> Average live cells per slice (last five minutes): 20.0 >> Maximum live cells per slice (last five minutes): 20 >> Average tombstones per slice (last five minutes): 1.0 >> Maximum tombstones per slice (last five minutes): 1 >> Dropped Mutations: 0 bytes >> >> -- >> >> regards, >> Laxmikant Upadhyay >> >> -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Alter composite column

t;>>> 2018-01-12 16:53 GMT+01:00 Joel Samuelsson <samuelsson.j...@gmail.com>: >>>> >>>>> 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: Alter composite column

tem (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 >>

Re: Many SSTables only on one node

ut I'm wondering, what was the cause? How prevent it from repeating? > > -- > Best Regards, > Dmitry Simonov > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Many SSTables only on one node

e run "repair -full" regulary for this keyspace (every 24 hours on each > node), because gc_grace_seconds is set to 24 hours. > > Should we consider increasing compaction throughput and > "concurrent_compactors" (as recommended for SSDs) to keep > "CompactionExe

Re: Nodetool repair multiple dc

uy exploring cassandra reaper ..does anyone has used that > in prod? > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Cassandra upgrade from 2.2.8 to 3.10

an you guys please let me know if this approach would work? I’m >> concerned if having mixed version on Cassandra nodes may cause any issues >> like in streaming data/sstables from existing DC to newly created third DC >> with version 3.10 installed, will nodes in DC3 join the cluster

Re: Cassandra | Cross Data Centre Replication Status

plicating on the Mum region's nodes. > However even after 2 weeks I do not see historical data to be replicated, > but new data being written on Sgp region is present in Mum region as well. > >>>> > >>>> Any help or suggestions to debug this issue will be highly > appreciated. > >>>> > >>>> Regards > >>>> Akshay Bhardwaj > >>>> +91-97111-33849 <+91%2097111%2033849> > >>>> > >>>> > >>> > >>> > >>> -- > >>> Jon Haddad > >>> http://www.rustyrazorblade.com > >>> twitter: rustyrazorblade > >>> > >>> > >> > >> > > > -- > Best Regards, > Kiran.M.K. > > - > 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: rolling version upgrade, upgradesstables, and vulnerability window

gradesstables is a node-local concern that doesn't impact streaming or >> node replacement or other situations since cassandra can read old version >> sstables and new sstables would simply be the new format. >> >> - >> 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: rolling version upgrade, upgradesstables, and vulnerability window

sstables as needed, and that > upgradesstables is a node-local concern that doesn't impact streaming or > node replacement or other situations since cassandra can read old version > sstables and new sstables would simply be the new format. > -- - Alexa

Re: Best compaction strategy

ionStrategy (LCS) >2. SizeTieredCompactionStrategy (STCS) >3. TimeWindowCompactionStrategy (TWCS) > > > -- > Raman Gugnani > > 8588892293 <(858)%20889-2293> > > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Compacting more than the actual used space

ging the compaction throughput to 0 (removing the > throttling), had no impacts in the current compaction. Do new compaction > throughput values only come into effect when a new compaction kicks in? > > Cheers > > Pedro Gordo > -- - Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com

  1   2   >