My experience to debug this kind of issue is to turn on trace. The nice
thing in cassandra is:
you can turn on trace only on 1 node and with a small percentage, i.e.
nodetool settraceprobability 0.05 --- only run on 1 node.
Hope it helps.
Regards,
James
On Thu, Jul 21, 2022 at 2:50 PM
I'd bet the JIRA that Paul is pointing to is likely what's happening
here. I'd look for read repair errors in your system logs or in your
metrics (if you have easy access to them).
There are operations that can happen during the course of a query
being executed that may happen at different
Yup, copy worked. Thanks.
On Thu, Jul 21, 2022 at 10:55 AM Nitan Kainth wrote:
> Use copy command or dsbulk
>
>
>
>
>
> Regards,
>
> Nitan K.
>
> 510-449-9629
>
>
>
>
>
> *From: *Arvinder Dhillon
> *Date: *Thursday, July 21, 2022 at 12:52 PM
> *To: *user@cassandra.apache.org
> *Subject:
Use copy command or dsbulk
Regards,
Nitan K.
510-449-9629
From: Arvinder Dhillon
Date: Thursday, July 21, 2022 at 12:52 PM
To: user@cassandra.apache.org
Subject: Export as csv
What tool do I use to dump a columns of a table having 40K partitions into a
csv file?
I tried caqsh with CAPTURE,
What tool do I use to dump a columns of a table having 40K partitions into
a csv file?
I tried caqsh with CAPTURE, it stuck after 100 rows and needs "enter" to
dump next 100, even with allow filtering.
Thanks,
Arvi
I came across this problem a few years ago, and had long conversations with
Datastax support about it.
In my case it turns out that the error message is misleading and I was pointed
to the ticket: https://issues.apache.org/jira/browse/CASSANDRA-14715
I con’t remember much about it now, but
Yes, I did it. Nothing like this in my code. Consistency level is set
only in one place (shown below).
On 7/21/22 4:08 PM, manish khandelwal wrote:
Consistency can also be set on a statement basis. So please check in
your code that you might be setting consistency 'ALL' for some queries.
On
It doesn't make any sense to see consistency level ALL if the code is
not explicitly using it. My best guess is somewhere in the code the
consistency level was overridden.
On 21/07/2022 14:52, pwozniak wrote:
Hi,
we have the following code (java driver):
cluster
Consistency can also be set on a statement basis. So please check in your
code that you might be setting consistency 'ALL' for some queries.
On Thu, Jul 21, 2022 at 7:23 PM pwozniak wrote:
> Hi,
>
> we have the following code (java driver):
>
> cluster =
Hi,
we have the following code (java driver):
cluster =Cluster.builder().addContactPoints(contactPoints).withPort(port)
.withProtocolVersion(ProtocolVersion.V3)
.withQueryOptions(new QueryOptions()
.setConsistencyLevel(ConsistencyLevel.QUORUM))
10 matches
Mail list logo
