On Tue, Jul 31, 2018 at 7:45 AM, onmstester onmstester
wrote:
> I need to do a full text search (like) on one of my clustering keys and
> one of partition keys (it use text as data type).
>
For simple LIKE queries on existing columns you could give SASI (
https://issues.apache.org/jira/browse/CASSANDRA-13289 is a new feature, not
yet available (its merged into trunk), that I believe will let you monitor
what you want.
On Sun, Jul 22, 2018 at 4:03 AM, onmstester onmstester
wrote:
> I'm using RF=2 and Write consistency = ONE, is there a counter in
>From the output you shared, it looks like you have at least one *very*
large partition — my guess is its lots of very small rows per partition.
This would explain why the slow compaction and why "nodetool stop
compaction" didn’t work (prior to CASSANDRA-14397 stop only works between
partitions).
Unfortunately, this can be pretty tricky to track down on the server. I’ve
filed https://issues.apache.org/jira/browse/CASSANDRA-14781 since I was
recently bit by this as well.
Jordan
On Mon, Sep 17, 2018 at 9:06 PM Saladi Naidu
wrote:
> Any clues on this topic?
>
> Naidu Saladi
>
>
> On
On Mon, Sep 17, 2018 at 10:52 PM onmstester onmstester
wrote:
> By adding new nodes to cluster, should i rebuild SASI indexes on all nodes
> ?
>
It isn’t necessary and will result in redundant work. On new nodes the
indexes will be built as data is streamed in. On existing nodes, compaction
or
Hi,
Have you tried batching calls to execute_async with periodic blocking for
the batch’s responses? I’ve witnessed this behavior as well with large or
no batches and while I didn’t have time to investigate fully its likely due
to message queuing behavior within Cassandra (pre-4.0). Smaller
I’m not very familiar with the python client unfortunately. If it helps: In
Java, async would return futures and at the end of submitting each batch
you would block on them by calling get.
Jordan
On Wed, Dec 11, 2019 at 1:37 AM lampahome wrote:
>
>
> Jordan West 於 2019年12月11日 週三
Hi Cassandra Users,
The Cassandra dev community is looking for users of Cassandra running on
windows to test compatibility of the 4.0 alpha / beta / rc releases.
If you run on windows and have time / resources to test, please report any
compatibility issues you find to the dev mailing list or
The bug reported in CASSANDRA-16735 [1] was known to cause corruption
thought to be recoverable but can, in fact, induce *non-recoverable*
corruption in some partitions. If you are not yet on 3.0.23, 3.0.24,
3.11.9, or 3.11.10, it is recommended you wait to upgrade until the
Cassandra community
