The short answer is that the OR and IN (which is basically OR under the hood)
operators are not supported yet in 5.0. See
https://issues.apache.org/jira/browse/CASSANDRA-19829
> On Aug 13, 2024, at 3:51 AM, Soheil Rahsaz wrote:
>
>
> Hello,
>
> I'm experimenting with SAI indexes and followi
ve to only have one database!
>
> I'll look into how to do profiling - the terms you use are things I'm not
> familiar with, but I've got chatGPT and google... :)
>
> -Joe
> On 3/21/2024 10:51 PM, Caleb Rackliffe wrote:
>
> To expand on Jonathan’s response, th
To expand on Jonathan’s response, the best way to get SAI to perform on the read side is to use it as a tool for large-partition search. In other words, if you can model your data such that your queries will be restricted to a single partition, two things will happen…1.) With all queries (not just
Yup, all repairs are complete. I'm reading at a CL of ONE pretty much
everywhere.
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:47487E9A-F738-4BAE-9A15-E6824E9D1834]
From: aaron morton mailto:aa...@thelastpickle.com>>
Reply-To: "user@cass
andra checks for TTL expirations. Does it happen
at compaction time? Some other time?
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:C02073B9-9A8A-49FE-89BE-9AC4419A3D3C]
From: "i...@4friends.od.ua<mailto:i...@4friends.od.ua>"
mailto:i...@4fri
eived certain mutations?) I ended up turning RR off entirely, since I've
got HH in place to handle short-duration failures :)
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:CA735F54-7FB9-4D56-8DD6-944F62768556]
From: aaron morton mailto:aa...@thelastpickle.c
That sounds right to me :)
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:8E620335-844B-4EFF-ACAB-3D4439A3B4B6]
From: Tamar Fraenkel mailto:ta...@tok-media.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org&
More detail…
I'm running 1.0.7 on these boxes, and the keyspace readout from the CLI looks
like this:
create keyspace Users
with placement_strategy = 'NetworkTopologyStrategy'
and strategy_options = {DC2 : 1, DC1 : 2}
and durable_writes = true;
Thanks!
Caleb Rackl
ork with a compromised cluster, etc.
I guess I'm wondering why your replication factor is set to 1…
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:3CCB142F-1DF5-423E-BF0E-4D8F3F31E15B]
From: Tamar Fraenkel mailto:ta...@tok-media.com>>
Reply-To: "user@cassan
tead of 20%.
Does anybody have any suggestions as to what might be going on? I've run
nodetool getendpoints against a bunch of keys, and I always get back three
nodes, so I'm pretty confused. I've also run repair on a few nodes in both
data centers, but the sizes are still vast
After some searching, I think I may have found something in the code itself,
and so I've filed a big report -
https://issues.apache.org/jira/browse/CASSANDRA-3711
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
From: Caleb Rackliffe mailto:ca...@steelhous
x27;t we just create a
pool with Runtime.availableProcessors() Threads and be done with it?
Let me know if I left any info out.
Thanks!
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
From: aaron morton mailto:aa...@thelastpickle.com>>
Reply-To: "user@c
threshold, low compaction T/P limit, and heavy write
load doesn't mean those threads are hanging around because they're actually not
done doing their compaction tasks.
Thanks,
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
Okay, it looks like I was slightly underestimating the number of connections
open on the cluster. This probably won't be a problem after I tighten up the
Hector pool maximums.
Sorry for the spam…
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
From:
I saw this article - http://comments.gmane.org/gmane.comp.db.cassandra.user/2225
I'm using the Hector client (for connection pooling), with ~3200 threads active
according to JConsole.
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
From: Caleb Rackliffe mail
One other item…
java –version
java version "1.7.0_01"
Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode)
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
From: Caleb Rackliffe
concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Has anybody seen this sort of problem before?
Thanks to anyone who takes a look. I can provide mo
emtable is
huge. Either way, the following line in Memtable looks a bit weird:
double newRatio = (double) deepSize / currentThroughput.get();
Has anyone seen this warning before?
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:835561CC-8141-473C-B2D5-344B8D34B499]
<>
e entries in my limits.conf for JNA:
rootsoftmemlock unlimited
roothardmemlock unlimited
Has anyone else seen this behavior?
Thanks,
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
[cid:51C98683-7807-40ED-992A-1FBF168FE2BD]
<>
Today, while bulk loading some data, I got the following message:
WARN [pool-1-thread-1] 2011-11-18 21:08:57,331 Memtable.java (line 172) setting
live ratio to maximum of 64 instead of 78.87903667214012
Should I be worried? If so, does anybody have any suggestions for how to
address it?
Thank
lt> rsult =
rangeSlicesQuery.execute();
…but no luck with the additional dimension.
Caleb Rackliffe | Software Developer
M 949.981.0159 | ca...@steelhouse.com
From: Guy Incognito mailto:dnd1...@gmail.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apac
t(), StringSerializer.get());
rangeSlicesQuery.setColumnFamily("Attributes");
rangeSlicesQuery.setKeys("id0", "id0");
rangeSlicesQuery.setRange("", "", true, 1);
QueryResult> rsult =
rangeSlicesQuery.execute();
…but no luck with the addi
22 matches
Mail list logo
