Re: consultant recommendations

Hey Randy Instaclustr provides consulting services for Cassandra as well as managed services if you are looking to offload the admin burden. https://www.instaclustr.com/services/cassandra-consulting/ Alternatively, send me an email

Re: Tombstone

TimeWindowCompactionStrategy and don’t delete the data you should be relying on Cassandra to drop the SSTables once the data inside has expired. THat 18% is probably waiting on gc_grace, this shouldn’t be an issue if you are letting TWCS drop the data rather then running deletes. Regards,

Re: Size of a single Data Row?

Hi Ralph, Yes, having partitions of 100mb will seriously hit your performance. But usually the issue here is for people handling large numbers of transactions and aiming for low latency. My understanding is the column value up to 2GB is it’s max. Like after that the system would start to fail,

Re: Single Host: Fix "Unknown CF" issue

s ago where a > datastax employee told me that we should not use materialized views - it is > better to create & fill all tables directly. > > Would you also recommend not to use materialized views? As this problem is > related to a view - maybe we could avoid this problem simply

Re: Single Host: Fix "Unknown CF" issue

Hi Michael, So I looked at the code, here are some stages of your error message: 1. at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:292) [apache-cassandra-3.11.0.jar:3.11.0 At this step Cassandra is running through the keyspaces in it’s schema turning off

Re: Single Host: Fix "Unknown CF" issue

Hey Michael, I have a hunch. If the system doesn’t recognise the column family which is stopping the node from starting perhaps try copying the column family directory to a backup then deleting it. Then restart Cassandra. If it starts I’ll assume the schema didn’t have the column family: *

Re: Adding new nodes to cluster to speedup pending compactions

Hi Mikhall, There are a few ways to speed up compactions in the short term: - nodetool setcompactionthroughput 0 This will unthrottle compactions but obviously unthrottling compactions puts you at risk of high latency while compactions are running. - nodetool setconcurrentcompactors 2 You

Re: Sorl/DSE Spark

ausing latency spikes in Cassandra which is not great > if you are are sensitive to that. > > > On Thu, 12 Apr 2018, 10:46 Evelyn Smith, <u5015...@gmail.com > <mailto:u5015...@gmail.com>> wrote: > Are you building a search engine -> Solr > Are you building

Re: Sorl/DSE Spark

Are you building a search engine -> Solr Are you building an analytics function -> Spark I feel they are used in significantly different use cases, what are you trying to build? If it’s an analytics functionality that’s seperate from your operations functionality I’d build it in it’s own DC.

Re: OOM after a while during compacting

t can cause different > kind of problems... Or the default secondary index? > > Thanks > > > > 2018-04-05 15:14 GMT+02:00 Evelyn Smith <u5015...@gmail.com > <mailto:u5015...@gmail.com>>: > Probably a dumb question but it’s good to clarify. > > Are y

Re: OOM after a while during compacting

compactors to 4 and unthrottle compactions by setting throughput to zero. This can help it catch up on those compactions. Then you can deal with trying a major compaction. Regards, Evelyn. > On 5 Apr 2018, at 11:14 pm, Evelyn Smith <u5015...@gmail.com> wrote: > > Probably a dumb qu

Re: OOM after a while during compacting

Probably a dumb question but it’s good to clarify. Are you compacting the whole keyspace or are you compacting tables one at a time? > On 5 Apr 2018, at 9:47 pm, Zsolt Pálmai wrote: > > Hi! > > I have a setup with 4 AWS nodes (m4xlarge - 4 cpu, 16gb ram, 1TB ssd each) >

Re: Many SSTables only on one node

It might not be what cause it here. But check your logs for anti-compactions. > On 5 Apr 2018, at 8:35 pm, Dmitry Simonov wrote: > > Thank you! > I'll check this out. > > 2018-04-05 15:00 GMT+05:00 Alexander Dejanovski