Re: How do TTLs generate tombstones

The TTL'd cell is treated as a tombstone. gc_grace_seconds applies to TTL'd cells, because even though the data is TTL'd, it may have been written on top of another live cell that wasn't ttl'd: Imagine a test table, simple key->value (k, v). INSERT INTO table(k,v) values(1,1); Kill 1 of the 3

How do TTLs generate tombstones

Hello, The following link says that TTLs generate tombstones - https://docs.datastax.com/en/cql/3.3/cql/cql_using/useExpire.html. What exactly is the process that converts the TTL into a tombstone? 1. Is an actual new tombstone cell created when the TTL expires? 2. Or, is the TTLed cell

Re: [EXTERNAL] Re: Increasing VNodes

Cant you just increase segmentCount option to split it more? On Wed, Oct 4, 2017 at 12:50 PM, Mohapatra, Kishore < kishore.mohapa...@nuance.com> wrote: > Thanks a lot for all of your input. We are actually using Cassandra > reaper. But it is just splitting the ranges into 256 per node. > > But I

Re: table repair question

Incremental repairs should also update the percentage, although I'd recommend not using incremental repair before 4.0. Just want to point out that running repairs based on repaired % isn't necessarily a bad thing, but it should be a secondary consideration. The important thing is to repair data

Re: table repair question

That percentage will only be updated if you do a full repair. If you do repairs on local dc or with -pr, that percentage will not be updated. I scripted a regular repair on each node based on if this percentage is below some threshold. It has been running fine since several months ago.

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Kurt, Thanks for your response. Created this ticket . Feel free to add anything to it that seems legit. Downloading Cassandra code right now. Fix seems quite simple. Expect a pull-request soon xD 2017-10-03 20:19 GMT-03:00 kurt greaves

UNSUBSCRIBE

__ Charley Rich VP, Product Management, jKool and Nastel cr...@nastel.com 631.761.9100x9128 linkedin.com/in/charleyrich [Nastel Technologies] The information contained in this e-mail and in any attachment is

RE: [EXTERNAL] Re: Increasing VNodes

Thanks a lot for all of your input. We are actually using Cassandra reaper. But it is just splitting the ranges into 256 per node. But I will certainly try out splitting into smaller ranges going thru the system.size_estimate table. Thanks Kishore Mohapatra Principal Operations DBA Seattle, WA

Re: Migrating a Limit/Offset Pagination and Sorting to Cassandra

Seems pretty overengineered, imo, given you can just save the pagination state as Andy Tolbert pointed out. > On Oct 4, 2017, at 8:38 AM, Daniel Hölbling-Inzko > wrote: > > Thanks for pointing me to Elassandra. > Have you had any experience running this in

Re: Increasing VNodes

The site (with the docs) is probably more helpful to learn about how reaper works: http://cassandra-reaper.io/ > On Oct 4, 2017, at 9:54 AM, Chris Lohfink wrote: > > Increasing number of tokens will make repairs worse not better. You can just

Re: Increasing VNodes

Increasing number of tokens will make repairs worse not better. You can just split the sub ranges into smaller chunks, you dont need to use vnodes to do that. Simple approach is to iterate through each host token range and split by N and repair them (ie

Re: Increasing VNodes

You don't need to change the number of vnodes, you can manually select CONTAINED token subranges and pass in -st and -et (just try to pick a number > 2^20 that is fully contained by at least one vnode). On Wed, Oct 4, 2017 at 9:46 AM, Mohapatra, Kishore < kishore.mohapa...@nuance.com> wrote:

Increasing VNodes

Hi, We are having a lot of problems in repair process. We use sub range repair. But most of the time, some ranges fails with streaming error or some other kind of error. So wondering if it will help if we increase the no. of VNodes from 256 (default) to 512. But increasing the VNodes

Re: Migrating a Limit/Offset Pagination and Sorting to Cassandra

Yes we’re using it in production in a 22 node cluster across 4 Amazon regions in a large production system. We were using DSE but recently migrated to it. There are a few quirks, (copy_to isn’t supported, for example), but so far been pretty pleased with it. - Greg > On Oct 4, 2017, at 8:38

Re: table repair question

Not really no. There's a repaired % in nodetool tablestats if you're using incremental repair (and you probably shouldn't be before 4.0 comes out), but I wouldn't make any decisions based off it's value. On October 4, 2017 at 8:05:44 AM, ZAIDI, ASAD A (az1...@att.com) wrote: Hello folk,  

Re: Migrating a Limit/Offset Pagination and Sorting to Cassandra

Thanks for pointing me to Elassandra. Have you had any experience running this in production at scale? Not sure if I I think ES will enter the picture at some point since some things just don't work efficiently with Cassandra and so it's inevitable in the end. But I'd rather delay that step for

Re: decommission mode with background compactors running

Streaming will grab a reference to the sstables so even if compacted they won’t be deleted until streamed - it’s safe as-is in terms of correctness, but may cause a temporary increase in disk usage as new writes happen and sstables are compacted together but old data files can’t be removed.

table repair question

Hello folk, I'm wondering if there is way to find out list of table(s) which need repair OR if there Is way to find out what %age of data would need to be repaired on a table? Is such information available from Cassandra db engine through some other means? TIA~ Asad

decommission mode with background compactors running

Hi list, I've decommission a node but in the background with nodetool status I've checked and there was 4 compactors running and simultaneously the SSTables sent to other nodes. Is this safe or we should disable all background process before decommission like: nodetool disableautocompaction

Re: Manual Compaction in cassandra

This is version dependent - in newer versions it’ll be one repaired and one I repaired (if you run repairs) -- Jeff Jirsa > On Oct 4, 2017, at 7:25 AM, Nitan Kainth wrote: > > There will be one table after major compaction for all existing tables. But > all new

Re: Manual Compaction in cassandra

There will be one table after major compaction for all existing tables. But all new sstable will keep on creating while compaction is in progress. Sent from my iPhone > On Oct 4, 2017, at 7:50 AM, Akshit Jain wrote: > > If Size Tiered Compaction Strategy is used, then

Re: Migrating a Limit/Offset Pagination and Sorting to Cassandra

Hi Daniel, To answer this question: > How long is the paginationState from the driver current? The paging state itself contains information about the position in data where to proceed from, so you don't need to worry about it becoming stale/invalid. The only exception is if you upgrade your

Manual Compaction in cassandra

If Size Tiered Compaction Strategy is used, then on performing manual compaction would there be always *1 sstable* at last irrespective of the size? Also would there be 2 sstables if repair has been performed?

Re: Read-/ Write Latency - Cassandra 2.1 .15 vs 3.10

Thanks for the info.. Thanks, Anumod Sent from my iPhone > On Oct 3, 2017, at 12:07 PM, Chris Lohfink wrote: > > RecentReadLatency metrics has been deprecated for years (1.1 or 1.2) and were > removed in 2.2. It was a very misleading metric. Instead pull from the >

Re: Materialized views stability

Ok, thanks for the info. This is what I wanted to know. Cheers, Hannu On 2 October 2017 at 18:27:16, Carlos Rolo (r...@pythian.com) wrote: I've been dealing with MV extensively, and I second Blake. MVs are not suitable for production. Unless you're ready for the pain (The out of sync is a major

Re: Alter table gc_grace_seconds

On Sun, Oct 1, 2017 at 4:14 PM, Gábor Auth wrote: > Hi, > > On Sun, Oct 1, 2017 at 3:44 PM Varun Barala > wrote: > >> This is the property of table and It's not written in sstables. If you >> change gc_grace, It'll get applied for all the data. >>

Re: Migrating a Limit/Offset Pagination and Sorting to Cassandra

Without knowing other details, of course, have you considered using something like Elassandra? That is a pretty tightly integrated Cassandra + Elastic Search solution. You’d insert data into Cassandra like you do normally, then query it with Elastic Search. Of course this would increase the

Re:

On Sun, Oct 1, 2017 at 6:14 PM, Bill Walters wrote: > Hi All, > > I need some help with deploying a monitoring and alerting system for our > new Cassandra 3.0.4 cluster that we are setting up in AWS East region. > I have a good experience with Cassandra as we are running

Re: Migrating a Limit/Offset Pagination and Sorting to Cassandra

Thanks Kurt, I thought about that but one issue is that we are doing limit/offset not pages. So one customer can choose to page through the list in 10 Item increments, another might want to page through with 100 elements per page. So I can't have a clustering key that represents a page range.