Thanks for the suggestions! Could altering the RF from 2 to 1 cause any
issues, or will it basically just be changing the coordinator's write paths
and also guiding future repairs/cleans?
On Wed, Jul 12, 2017 at 22:29 Jeff Jirsa wrote:
>
>
> On 2017-07-11 20:09 (-0700), "Kevin O'Connor"
> wrote
On 2017-07-11 20:09 (-0700), "Kevin O'Connor" wrote:
> This might be an interesting question - but is there a way to truncate data
> from just a single node or two as a test instead of truncating from the
> entire cluster? We have time series data we don't really care if we're
> missing gaps in
On 2017-07-12 12:03 (-0700), Fay Hou [Storage Service] Â
wrote:
> First, a big thank to Jeff who spent endless time to help this mailing list.
> Agreed that we should tune the key cache. In my case, my key cache hit rate
> is about 20%. mainly because we do random read. We just going to leave
First, a big thank to Jeff who spent endless time to help this mailing list.
Agreed that we should tune the key cache. In my case, my key cache hit rate
is about 20%. mainly because we do random read. We just going to leave the
index_interval as is for now.
On Mon, Jul 10, 2017 at 8:47 PM, Jeff Ji
Hi,
According to SASI source code (3.11.0) it will always have priority over
regular secondary index:
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/index/sasi/SASIIndex.java#L234
public long getEstimatedResultRows()
{
// this is temporary (
In the original source code Sasi will be chosen instead of secondary index
Le 12 juil. 2017 09:13, "Vlad" a écrit :
> Hi,
>
> it's possible to create both regular secondary index and SASI on the same
> column:
>
>
>
>
> *CREATE TABLE ks.tb (id int PRIMARY KEY, name text);CREATE CUSTOM INDEX
> t
Probably worth mentioning that some operational procedures like repairs,
bootstrapping etc are helped massively by using less tokens. Incremental
repairs are one of the things I would say is most impacted the by it since
less tokens will mean less local ranges to iterate through and less anti
compa
Hi,
it's possible to create both regular secondary index and SASI on the same
column:
CREATE TABLE ks.tb (id int PRIMARY KEY, name text);
CREATE CUSTOM INDEX tb_name_idx_1 ON ks.tb (name) USING
'org.apache.cassandra.index.sasi.SASIIndex';
CREATE INDEX tb_name_idx ON ks.tb (name);
But which one
Hi Carlos Rolo
Using LOCAL_QUORUM for both writes & reads.
I see there is a time difference of 2 mins among nodes, I think that could
be the reason.
Anyways thanks for replying Carlos Rolo...
Have a nice day... :)
On Wed, Jul 12, 2017 at 12:45 AM, Carlos Rolo wrote:
> What consistency are you u
