Hi There,
I need some suggestions in terms of connecting to the Cassandra cluster
which is deployed on the Kubernetes cluster via the datastax client library.
The idea is to expose Kubernetes Service object for the Cassandra
cluster which can be leveraged by a client which is using the datastax
Thanks Erick! It is clear now.
On Tue, Sep 7, 2021 at 4:07 PM Erick Ramirez
wrote:
> No, I'm just saying that [-pr] is the same as [-pr -full], NOT the same as
> just [-full] on its own. Primary range repairs are not compatible with
> incremental repairs so by definition, -pr is a [-pr -full]
Thanks Erick for the response. So in option 3, -pr is not taken into
consideration which essentially means option 3 is the same as option 1
(which is the full repair).
Right, just want to be sure?
Best,
Deepak
On Tue, Sep 7, 2021 at 3:41 PM Erick Ramirez
wrote:
>
>1. Will perform a full
Hi There,
We are on Cassandra 3.0.11 and I want to understand what is the
difference between following two commands
1. nodetool repair -full
2. nodetool repair -pr
3. nodetool repair -full -pr
As per my understanding 1. will do the full repair across all keyspaces. 2.
with -pr, restricts repair
= resultSet.iterator();
while (iter.hasNext()) {
if (resultSet.getAvailableWithoutFetching() <= fetchSize &&
!resultSet.isFullyFetched()) {
resultSet.fetchMoreResults();
}
Row row = iter.next();
.
}
Thanks,
Deepak
On Sat, Sep 19, 2020 at 6:56 PM Deepak Sharma
wrote
he table definition (PRIMARY KEY, specifically).
> 3) Maybe a little description of what the table is designed to do.
> 4) How much data you're expecting returned (both # of rows and data size).
>
> Thanks,
>
> Aaron
>
>
> On Mon, Sep 14, 2020 at 10:58 AM Deepak Sha
Hi There,
We are running into a strange issue in our Cassandra Cluster where one
specific query is failing with following error:
Cassandra timeout during read query at consistency QUORUM (3 responses were
required but only 0 replica responded)
This is not a typical query read timeout that we
Thanks! That's what I realized later too.
On Tue, Jun 2, 2020 at 9:57 AM Jeff Jirsa wrote:
> It's marked as a duplicate of
> https://issues.apache.org/jira/browse/CASSANDRA-10699 which is not yet
> fixed
>
>
> On Tue, Jun 2, 2020 at 9:39 AM Deepak Sharma
> wrote:
>
Hi There,
I see this (https://issues.apache.org/jira/browse/CASSANDRA-11143) issue in
the resolved state. Does it mean it has been fixed? This question is
specific in the context of 3.0.13 and 3.11.4 versions of Cassandra.
Thanks,
Deepak
Hi There,
We have a use case where we need to have two separate PreparedStatement
objects (one with RetryPolicy and the other without any retry policy) for
the same query string. And when we try to create two separate
PreparedStatements, we see only one PreparedStatement getting retained (the
10 matches
Mail list logo
