Re: Tombstoned error and then OOM

2016-10-06 Thread kurt Greaves
; > Here the status is integer column which is indexed. > > -- IB > > -- > *From:* kurt Greaves > *To:* user@cassandra.apache.org; INDRANIL BASU > *Sent:* Tuesday, 4 October 2016 10:38 PM > *Subject:* Re: Tombstoned error and then OOM > >

Re: Tombstoned error and then OOM

2016-10-04 Thread INDRANIL BASU
, 4 October 2016 10:38 PM Subject: Re: Tombstoned error and then OOM This sounds like you're running a query that consumes a lot of memory. Are you by chance querying a very large partition or not bounding your query? I'd also recommend upgrading to 2.1.15, 2.1.0 is very old and h

Re: Tombstoned error and then OOM

2016-10-04 Thread kurt Greaves
This sounds like you're running a query that consumes a lot of memory. Are you by chance querying a very large partition or not bounding your query? I'd also recommend upgrading to 2.1.15, 2.1.0 is very old and has quite a few bugs. On 3 October 2016 at 17:08, INDRANIL BASU wrote: > Hello All,

Tombstoned error and then OOM

2016-10-03 Thread INDRANIL BASU
Hello All, I am getting the below error repeatedly in the system log of C* 2.1.0 WARN  [SharedPool-Worker-64] 2016-09-27 00:43:35,835 SliceQueryFilter.java:236 - Read 0 live and 1923 tombstoned cells in test_schema.test_cf.test_cf_col1_idx (see tombstone_warn_threshold). 5000 columns was requ