Re: Old tombstones not being cleaned up

ch >> means it won’t purge the tombstone if it shadows data in the unrepaired set >> >> >> >> -- >> Jeff Jirsa >> >> >> On Feb 12, 2018, at 12:46 AM, Bo Finnerup Madsen >> wrote: >> >> Well for anyone having the same issue,

Re: Old tombstones not being cleaned up

..@dynatrace.com>: > >> Right. In this case, cleanup should have done the necessary work here. >> >> >> >> Thomas >> >> >> >> *From:* Bo Finnerup Madsen [mailto:bo.gunder...@gmail.com] >> *Sent:* Freitag, 02. Februar 2018 06:59 >> >>

Re: Old tombstones not being cleaned up

> TTL, then nodes might not see the deletes anymore, as a node might not own > the partition anymore after a topology change (e.g. scale out beyond the > keyspace RF). > > > > Just a very wild guess. > > > > Thomas > > > > *From:* Bo Finnerup Madsen [mai

Re: Old tombstones not being cleaned up

the TTL on the existing data, only > new data. It’s only set if you don’t supply one yourself. > > > > On Wed, Jan 31, 2018 at 11:35 PM Bo Finnerup Madsen < > bo.gunder...@gmail.com> wrote: > > Hi, > > > > We are running a small 9 node Cassandra v2.1.17 clust

Re: Old tombstones not being cleaned up

t; > On Wed, Jan 31, 2018 at 11:35 PM Bo Finnerup Madsen < > bo.gunder...@gmail.com> wrote: > >> Hi, >> >> We are running a small 9 node Cassandra v2.1.17 cluster. The cluster >> generally runs fine, but we have one table that are causing OOMs because an >&

Re: Old tombstones not being cleaned up

if it's last, it will have to stay until > next level compaction happens, then will be gone, right ? > > On Thu, Feb 1, 2018 at 2:33 AM, Bo Finnerup Madsen > wrote: > >> Hi, >> >> We are running a small 9 node Cassandra v2.1.17 cluster. The cluster >> ge

Old tombstones not being cleaned up

Hi, We are running a small 9 node Cassandra v2.1.17 cluster. The cluster generally runs fine, but we have one table that are causing OOMs because an enormous amount of tombstones. Looking at the data in the table (sstable2json), the first of the tombstones are almost a year old. The table was init

Re: When are hints written?

e", that > essentially means that a node hasn't acknowledged back > to the coordinator that the write succeeded within > write_request_timeout_in_ms. This includes TCP/socket > timeouts, connection issues or that the node is down. The > hints are stored for a maximum timespa

Re: When are hints written?

ints are stored for a > maximum timespan defaulting to 3 hours. > > Cheers, > Jens > > On Thu, Apr 21, 2016 at 8:06 AM Bo Finnerup Madsen > wrote: > >> Hi Jens, >> >> Thank you for the tip! >> ALL would definitely cure our hints issue, but as you note,

Re: When are hints written?

> > Cheers, > Jens > > On Wed, Apr 20, 2016 at 3:39 PM Bo Finnerup Madsen > wrote: > >> Hi, >> >> We have a small 5 node cluster of m4.xlarge clients that receives writes >> from ~20 clients. The clients will write as fast as they can, and the whole >&g

When are hints written?

Hi, We have a small 5 node cluster of m4.xlarge clients that receives writes from ~20 clients. The clients will write as fast as they can, and the whole process is limited by the write performance of the cassandra cluster. After we have tweaked our schema to avoid large partitions, the load is goi

Debugging out of memory

Hi, We have an application that reads data from a set of external sources and loads them into our cassandra cluster. The load goes ok for some time (~24h) and then some servers in the cluster starts flapping between being down and up, and finally they go out of memory. The cluster consists of 5 m4

Re: Data modelling, including cleanup

materialised views so that you don’t need > to keep two tables up to date manually: > http://www.datastax.com/dev/blog/new-in-cassandra-3-0-materialized-views > > Hannu > > On 17 Mar 2016, at 12:05, Bo Finnerup Madsen > wrote: > > Hi, > > We are pretty new to data

Re: Experiencing strange disconnect issue

d and the driver is not > retrying hosts once they are marked “down.” > > > > > > Sean Durity – Lead Cassandra Admin > > Big DATA Team > > For support, create a JIRA > <https://portal.homedepot.com/sites/bigdata/Shared%20Documents/Jira%20Hadoop%20Support%20

Re: Experiencing strange disconnect issue

licy(1000,3)) > > or something similar to your cluster builder. > > Steve > > > On Wed, Mar 16, 2016 at 11:18 AM, Bo Finnerup Madsen < > bo.gunder...@gmail.com> wrote: > >> Hi Sean, >> >> Thank you for taking the time to answer :) >

Re: Experiencing strange disconnect issue

something similar to your cluster builder. > > Steve > > > On Wed, Mar 16, 2016 at 11:18 AM, Bo Finnerup Madsen < > bo.gunder...@gmail.com> wrote: > >> Hi Sean, >> >> Thank you for taking the time to answer :) >> We are using a very vanilla con

Data modelling, including cleanup

Hi, We are pretty new to data modelling in cassandra, and are having a bit of a challenge creating a model that caters both for queries and updates. Let me try to explain it using the users example from http://www.datastax.com/dev/blog/basic-rules-of-cassandra-data-modeling They define two table

Experiencing strange disconnect issue

Hi, We are currently trying to convert an existing java web application to use cassandra, and while most of it works great :) we have a "small" issue. After some time, we all connectivity seems to be lost and we get the following errors: com.datastax.driver.core.exceptions.NoHostAvailableExceptio