Re: Cassandra Needs to Grow Up by Version Five!

Brotman > > -----Original Message- > From: Daniel Hölbling-Inzko [mailto:daniel.hoelbling-in...@bitmovin.com] > Sent: Tuesday, February 20, 2018 1:28 AM > To: user@cassandra.apache.org; James Briggs > Cc: d...@cassandra.apache.org > Subject: Re: Cassandra Needs to Grow Up

Re: Cassandra Needs to Grow Up by Version Five!

Hi, I have to add my own two cents here as the main thing that keeps me from really running Cassandra is the amount of pain running it incurs. Not so much because it's actually painful but because the tools are so different and the documentation and best practices are scattered across a dozen

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

gt; 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 < > daniel.hoelbling-in...@bitmovin.com> wrote: > > Thanks for pointing me to Elassandra. >

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

> - Greg > > > On Oct 3, 2017, at 11:10 PM, Daniel Hölbling-Inzko < > daniel.hoelbling-in...@bitmovin.com> wrote: > > 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

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

ion if in-mem sorting > isn't an option, if this is true you will want to be wary of creating large > partitions and reading them all at once. Although this depends on your data > model and compaction strategy choices. > > On 3 October 2017 at 08:36, Daniel Hölbling-Inzko < > d

Migrating a Limit/Offset Pagination and Sorting to Cassandra

Hi, I am currently working on migrating a service that so far was MySQL based to Cassandra. Everything seems to work fine so far, but a few things in the old services API Spec is posing some interesting data modeling challenges: The old service was doing Limit/Offset pagination which is obviously

Re: Datastax Driver Mapper & Secondary Indexes

https://pantheon.io/blog/cassandra-scale-problem-secondary-indexes might > help. > > On 26 September 2017 at 07:17, Daniel Hölbling-Inzko < > daniel.hoelbling-in...@bitmovin.com> wrote: > >> Hi, >> I am currently moving an application from SQL to Cassandra using Java. I

Datastax Driver Mapper & Secondary Indexes

Hi, I am currently moving an application from SQL to Cassandra using Java. I successfully got the DataStax driver and the mapper up and running, but can't seem to figure out how to set secondary indexes through the mapper. I also can't seem to find anything related to indexes in the mapper sources

Re: Bootstrapping a new Node with Consistency=ONE

the data yet so a repair needs to be run. Awesome - thanks so much. greetings Daniel On Thu, 3 Aug 2017 at 09:56 Oleksandr Shulgin <oleksandr.shul...@zalando.de> wrote: > On Thu, Aug 3, 2017 at 9:33 AM, Daniel Hölbling-Inzko < > daniel.hoelbling-in...@bitmovin.com> wrote: > >&

Re: Bootstrapping a new Node with Consistency=ONE

se? > > > -- > Jeff Jirsa > > > On Aug 2, 2017, at 11:52 PM, Daniel Hölbling-Inzko < > daniel.hoelbling-in...@bitmovin.com> wrote: > > Thanks Jeff. How do I determine that bootstrap is finished? Haven't seen > that anywhere so far. > > Reads via storage

Re: Bootstrapping a new Node with Consistency=ONE

service (tcp/7000), but the guarantee is that data should be consistent by > the time bootstrap finishes > > > > > -- > Jeff Jirsa > > > > On Aug 2, 2017, at 1:53 AM, Daniel Hölbling-Inzko < > daniel.hoelbling-in...@bitmovin.com> wrote: > > >

Re: Bootstrapping a new Node with Consistency=ONE

Thanks for the pointers Kurt! I did increase the RF to N so that would not have been the issue. DC migration is also a problem since I am using the Google Cloud Snitch. So I'd have to take down the whole DC and restart anew (which would mess with my clients as they only connect to their local

Bootstrapping a new Node with Consistency=ONE

Hi, It's probably a strange question but I have a heavily read-optimized payload where data integrity is not a big deal. So to keep latencies low I am reading with Consistency ONE from my Multi-DC Cluster. Now the issue I saw is that I needed to add another Cassandra node (for redundancy

Re: Data Loss irreparabley so

In that vein, Cassandra support Auto compaction and incremental repair. Does this mean I have to set up cron jobs on each node to do a nodetool repair or is this taken care of by Cassandra anyways? How often should I run nodetool repair Greetings Daniel Jeff Jirsa schrieb am

Re: Understanding gossip and seeds

Seeds are there to bootstrap a node for the very first time when it's has zero knowledge about the ring. I think I also read somewhere that seed nodes are periodically queried for some sanity checks and therefore one should not include too many nodes in the seed list. kurt greaves

Re: Don't print Ping caused error logs

Just out of curiosity how to you then make sure all nodes get the same amount of traffic from clients without having to maintain a manual contact points list of all cassandra nodes in the client applications? Especially with big C* deployments this sounds like a lot of work whenever

Re: Cassandra Snapshots and directories

When you call nodetool snapshot, it will create a directory with snapshot > name if specified or current timestamp at > /data///backup/. This directory will > have all sstables, metadata files and schema.cql (if using 3.0.9 or higher). > > > On Thu, May 11, 2017 at 2:

Cassandra Snapshots and directories

Hi, I am going through this guide to do backup/restore of cassandra data to a new cluster: http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_backup_snapshot_restore_t.html#task_ds_cmf_11r_gk When creating a snapshot I get the snapshot files mixed in with the normal data files and

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

If you have to allow filtering for the query to work it usually always results in a table scan. greetings Daniel On Tue, 9 May 2017 at 15:33 Jon Haddad wrote: > I don’t see any way it wouldn’t. Have you tried tracing it? > > > On May 9, 2017, at 8:32 AM, Kant Kodali

Re: A Single Dropped Node Fails Entire Read Queries

n't fail the query when I dropped it. The nodes were installed and > configured with Puppet so the configuration is the same on all 3 nodes. > > > Thanks! > > > > On Fri, Mar 10, 2017 at 10:25 AM, Daniel Hölbling-Inzko < > daniel.hoelbling-in...@bitmovin.com>

Re: A Single Dropped Node Fails Entire Read Queries

The LOCAL_QUORUM works on the available replicas in the dc. So if your replication factor is 2 and you have 10 nodes you can still only loose 1. With a replication factor of 3 you can loose one node and still satisfy the query. Ryan Svihla schrieb am Do. 9. März 2017 um 18:09: