Re: Cassandra Schema version mismatch

I've heard about this ... how did the problem present itself? Sent from my iPhone > On May 5, 2017, at 3:17 PM, Jeff Jirsa wrote: > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth wrote: >> Hi Experts, >> >> We found schema version mismatch in our

Re: Cassandra Schema version mismatch

Generally shouldn't happen in most modern versions of cassandra. Could be simultaneous conflicting statements (two "CREATE TABLE" statements at the same time, which can happen with programatic schema changes), or unhealthy schema tables (lots and lots of changes create tombstones in the schema

Re: DTCS to TWCS

Thanks Jeff Thanks, Vasu > On May 5, 2017, at 5:22 PM, Jeff Jirsa wrote: > > > >> On 2017-05-04 14:08 (-0700), Jon Haddad wrote: >> We (The Last Pickle) wrote a blog post on using TWCS pre-3.0: >>

Re: Cassandra Schema version mismatch

No, just two nodes have mismatch out of 18 nodes. We upgraded long back. Sent from my iPhone > On May 5, 2017, at 5:17 PM, Jeff Jirsa wrote: > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth wrote: >> Hi Experts, >> >> We found schema version

Re: DTCS to TWCS

On 2017-05-04 14:08 (-0700), Jon Haddad wrote: > We (The Last Pickle) wrote a blog post on using TWCS pre-3.0: > http://thelastpickle.com/blog/2017/01/10/twcs-part2.html > > > Alex Dejanovski wrote a very

Re: Cassandra Schema version mismatch

On 2017-05-05 11:00 (-0700), Nitan Kainth wrote: > Hi Experts, > > We found schema version mismatch in our cluster. We fixed it by bouncing C* > on nodes where version was mismatched. Can someone suggest, what are the > possible reasons for this? We are trying to figure

Re: manual deletes with TWCS

This is involving TTLed data, and I actually would want to delete all related partitions across all time windows. Let's say I have a time series partitioned by day with a 7 day TTL and a window size of one day. If I delete partitions for the past seven days, would I still run into the issue of

Re: manual deletes with TWCS

You cannot. From Alex’s TLP post: http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html TWCS is no fit for workload that perform deletes on non TTLed data. Consider that SSTables from different time windows will never be compacted

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

Re: Smart Table creation for 2D range query

I think you’ll want to model your table similar to how an R-Tree [1] / Quad tree [2] works. Let’s suppose you had a 10x10 meter land area and you wanted to put stuff in there. In order to find “all the things in point x,y”, you could break your land area into a grid. A partition would

New Cassandra Luxembourg Meetup

Moein all! I have just started a new Cassandra Luxembourg meetup if people are interested (and why would you not)! https://www.meetup.com/Cassandra-Luxembourg/ My company will sponsor and schedule some talks etc.. if there is enough demand. So

New Cassandra Luxembourg Meetup

Moein all! I have just started a new Cassandra Luxembourg meetup if people are interested (and why woul you not)! https://www.meetup.com/Cassandra-Luxembourg/ My company will sponsor and schedule some talks etc.. if there is enough demand. So sign up - could be interesting!! Johnny -- --

Re: Smart Table creation for 2D range query

Make metadata as partition key and x,y as part of partition key i.e. Primary key. It should work Sent from my iPhone > On May 5, 2017, at 2:40 PM, Lydia wrote: > > Hi all, > > I am new to Apache Cassandra and I would like to get some advice on how to > tackle a

Smart Table creation for 2D range query

Hi all, I am new to Apache Cassandra and I would like to get some advice on how to tackle a table creation / indexing in a sophisticated way. My aim is to store x- and y-coordinates, accompanied by some columns with meta information (m1, ... ,m5). There will be around 100,000,000 rows overall.

Re: Cassandra Schema version mismatch

No schematic change! Sent from my iPhone > On May 5, 2017, at 2:30 PM, Carlos Rolo wrote: > > Are you changing the schema in a dynamic fashion? If you get problems > (network, gc pauses, etc) during the schema changes it might lead to that. > > Regards, > > Carlos Juzarte

Re: Cassandra as a key/object store for many small (10-60k) files

I would guess you have network overload issues, I have seen pretty much exactly what you describe many times, (so far ;{) always this is the issue. Especially with 1gbit networks, no jumbo frames, etc. Get your network guys to monitor the error retry packets across ALL of the interfaces (all the

Re: Cassandra Schema version mismatch

Are you changing the schema in a dynamic fashion? If you get problems (network, gc pauses, etc) during the schema changes it might lead to that. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter:

Re: Cassandra as a key/object store for many small (10-60k) files

Yes, local storage volumes on each machine. > On May 5, 2017, at 3:25 PM, daemeon reiydelle wrote: > > These numbers do not match e.g. AWS, so guessing you are using local storage? > > > ... > Making a billion dollar startup is easy: "take a human desire, preferably

Re: Cassandra as a key/object store for many small (10-60k) files

These numbers do not match e.g. AWS, so guessing you are using local storage? *...* *Making a billion dollar startup is easy: "take a human desire, preferably one that has been around for a really long time … Identify that desire and use modern technology to take out steps."*

Cassandra as a key/object store for many small (10-60k) files

Hello, We’re currently testing Cassandra for use as a pure key-object store for data blobs around 10kB - 60kB each. Our use case is storing on the order of 10 billion objects with about 5-20 million new writes per day. A written object will never be updated or deleted. Objects will be read at

Cassandra Schema version mismatch

Hi Experts, We found schema version mismatch in our cluster. We fixed it by bouncing C* on nodes where version was mismatched. Can someone suggest, what are the possible reasons for this? We are trying to figure out the root cause. thank you!

Re: Totally unbalanced cluster

Hi, Regarding the documentation I've already knew: - thelastpickle.com/blog/2016/07/27/about-deletes-and-tombstones.html (From myself, how to handle tombstones) - http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html

Re: Totally unbalanced cluster

Hi, > but it's so easy to add nodes Apache Cassandra has some kind of magic pieces ;-). Sometimes it is dark magic though :p. Yet adding a node is indeed not harder when using NetworkTopologyStrategy, as Jon mentioned above, once the configuration is done once properly. > Number of keys

Re: [Cassandra] nodetool compactionstats not showing pending task.

Hi, Sorry to hear the restart did not help. Maybe try to monitor through JMX with 'org.apache.cassandra.db:type=CompactionManager', > attribute 'Compactions' or 'CompactionsSummary' What is this attribute showing? Here is the Apache Cassandra Jira:

Re: Very slow cluster

Thank you Anthony. Eduardo Alonso Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224 Pozuelo de Alarcón, Madrid Tel: +34 91 828 6473 // www.stratio.com // *@stratiobd * 2017-05-01 2:27 GMT+02:00 Anthony Grasso : > Hi Eduardo, > >