Re: Cassandra 3.11 is compacting forever

try to do a rolling restart for the cluster before doing a compation On Fri, Sep 1, 2017 at 3:09 PM, Igor Leão wrote: > Some generic errors: > > *[aladdin@ip-172-16-1-10 cassandra]$ tail cassandra.log | grep -i error* > *[aladdin@ip-172-16-1-10 cassandra]$ tail cassandra.log

Re: How to check if repair is actually successful

At the end of the repair, you should see something like: [2017-09-01 06:59:04,699] Repair completed successfully [2017-09-01 06:59:04,704] Repair command #1 finished in X hour X minutes X seconds On Fri, Sep 1, 2017 at 9:51 AM, Blake Eggleston wrote: > If nodetool repair

Re: nodetool repair failure

What is your GC_GRACE_SECONDS ? What kind repair option do you use for nodetool repair on a keyspace ? Did you start the repair on one node? did you use nodetool repair -pr ? or just "nodetool repair keyspace" ? How many nodetool repair processes do you use on the nodes? On Sun, Jul 30, 2017

Re: Cassandra crashes....

.apache.org" <user@cassandra.apache.org> *Subject: *Re: Cassandra crashes 16GB heap is too small for G1GC . Try at least 32GB of heap size On Tue, Aug 22, 2017 at 7:58 AM Fay Hou [Storage Service] ­ < fay...@coupang.com> wrote: What errors do you see? 16gb of 256 GB . H

Re: Cassandra crashes....

What errors do you see? 16gb of 256 GB . Heap is too small. I would give heap at least 160gb. On Aug 22, 2017 7:42 AM, "Thakrar, Jayesh" wrote: Hi All, We are somewhat new users to Cassandra 3.10 on Linux and wanted to ping the user group for their experiences.

Re: Creating a copy of a C* cluster

We do snapshot and sstableloader. with sstableloader, it is ok to have different configuration of the "stand by" cluster (i.e. number of the nodes). however, there is a issue we ran into with the sstableloader (java.lang.OutOfMemoryError: GC overhead limit exceeded)

Re: SASI index returns no results

SASI is in early experiment and had many major problems. for example, "nodetool repair breaks SASI index" https://issues.apache.org/jira/browse/CASSANDRA-13403 "OOM when using SASI index" https://issues.apache.org/jira/browse/CASSANDRA-12662 I would not use SASI index for production. Fay On

Re: performance penalty of add column in CQL3

are you aware this ticket? https://issues.apache.org/jira/browse/CASSANDRA-13004 On Tue, Jul 25, 2017 at 1:23 PM, Boris Iordanov wrote: > Hi, > > Is "alter table t add column..." an expensive operation? For example, if > it's something to be triggered at an admin level

Re: Cassandra seems slow when having many read operations

Hey Felipe: When you say increased memory from 16GB to 24GB, I think you meant you increased heap to 24GB. do you use cms or g1gc? did you change any other parameters? As for the chunk size, we found change 64kb to 16kb didn't make a difference in low key cache rate environment On Fri, Jul

Re: index_interval

Jirsa <jji...@apache.org> wrote: > > > On 2017-07-10 15:09 (-0700), Fay Hou [Storage Service] ­ < > fay...@coupang.com> wrote: > > BY defaults: > > > > AND max_index_interval = 2048 > > AND memtable_flush_period_in_ms = 0 > > AND min_i

index_interval

BY defaults: AND max_index_interval = 2048 AND memtable_flush_period_in_ms = 0 AND min_index_interval = 128 "Cassandra maintains index offsets per partition to speed up the lookup process in the case of key cache misses (see cassandra read path overview

Re: Repair on system_auth

There is a bug on repair system_auth keyspace. We just skip the repair on system_auth. Yes. it is ok to kill the running repair job On Thu, Jul 6, 2017 at 1:14 PM, Subroto Barua wrote: > you can check the status via nodetool netstats > to kill the repair job,

Re: Manual Repairs

what version of your cassandra and what kind repair you are doing? full repair or incremental repair? list your repair command On Wed, Jun 21, 2017 at 3:27 PM, Mark Furlong wrote: > Can a repair be paused, and if paused can it be restarted from the point > of the pause,