oughput for sure.
>
>
>
> http://www.datastax.com/dev/blog/java-driver-async-queries
>
>
>
>
>
> On Sat, Mar 18, 2017 at 08:00 S G wrote:
>
> I have enabled JMX but not sure what metrics to look for - they are way
> too many of them.
>
> I am using s
Cassandra cluster with
16 VMs, 8-core each too.
Thanks
SG
On Sat, Mar 18, 2017 at 5:38 PM, S G wrote:
> Thanks. It seems that you guys have found executeAsync to yield good
> results.
> I want to share my understanding how this could benefit performance and
> some validation
Forgot to mention that this vmstat picture is for the client-cluster
reading from Cassandra.
On Sat, Mar 18, 2017 at 6:47 PM, S G wrote:
> ok, I gave the executeAsync() a try.
> Good part is that it was really easy to write the code for that.
> Bad part is that it did not had a huge
Hi,
I have several non-primitive columns in my cassandra tables.
Some of them are user-defined-types UDTs.
While querying them through datastax driver, I want to convert such UDTs
into JSON values.
More specifically, I want to get JSON string for the value object below:
Row row = itr
Hi,
I have a keyspace with two tables.
I run a different query for each table:
Table 1:
Select * from table1 where id = ?
Table 2:
Select * from table2 where id1 = ? and id = ?
My code using datastax fires above two queries one after the other.
While it never fails for table 1, it never s
Ah, the keyspace for table2 was somehow getting hardcoded to a wrong
keyspace.
Wish the error message a little more helpful.
On Fri, Mar 24, 2017 at 2:48 PM, S G wrote:
> Hi,
>
> I have a keyspace with two tables.
>
> I run a different query for each table:
>
> Table
ahoo Mail on Android
>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>>
>> On Sat, Mar 25, 2017 at 3:19 AM, S G
>> wrote:
>> Hi,
>>
>> I have a keyspace with two tables.
>>
>> I run a different query for each table:
>&
Hi,
I have a bigint field in my Cassandra that I want to convert to a long
value. However, I am not sure how to specify the same in my
DataStax-mapper-entity-class.
Here is the code:
@PartitionKey(1)
@Column(name="phone", codec=TypeCodec.)
private Double phoneNumber;
Can someone please tell wha
Hello,
As mentioned in https://cassandra.apache.org/_/cassandra-basics.html, can
someone clarify how many coordinator nodes are there in the cluster at any
given time?
1. Is there a dedicated *single* coordinator node in the whole cluster
that changes from time to time?
2. Or any node be
Hello,
Does anyone know if opensource Cassandra support mutual-TLS ?
The documentation doesn't conclusively deny or accept the support for the
same.
Thanks !
>
> > On Sep 21, 2021, at 11:59 AM, S G wrote:
> >
> > Hello,
> >
> > Does anyone know if opensource Cassandra support mutual-TLS ?
> > The documentation doesn't conclusively deny or accept the support for
> the same.
> >
> > Thanks !
>
>
Hello,
Is there a way to stop long running queries in Cassandra (versions 3.11.x
or 4.x) ?
The use-case is to have some kind of a circuit breaker based on query-time
that has exceeded the client's SLAs.
Example: If server response is useless to the client after 10 ms, then we
could
have a *query_k
out values do this today.
>
>
> https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L920-L943
>
>
> On Tue, Oct 12, 2021 at 9:53 AM S G wrote:
>
>> Hello,
>>
>> Is there a way to stop long running queries in Cassandra (versions 3.11.x
>> or
It sends an exception to the client, it doesnt sever the connection.
>
>
> On Tue, Oct 12, 2021 at 10:06 AM S G wrote:
>
>> Do the timeout values only kill the connection with the client or send
>> error to the client?
>> Or do they also kill the corresponding
12, 2021 at 10:49 AM Bowen Song wrote:
> That will depend on whether you have cross_node_timeout enabled. However,
> I have to point out that set timeout to 15ms is perhaps not a good idea,
> the JVM GC can easily cause a lots of timeouts.
> On 12/10/2021 18:20, S G wrote:
&g
Hello,
Does anyone know about the default being turned off for this setting?
It seems like a good one to be turned on - why have replicas process
something for which coordinator has already sent the timeout to client?
Thanks
On Tue, Oct 12, 2021 at 11:06 AM S G wrote:
> Thanks Bowen.
&g
Hello,
We have frequently seen that a single bad node running slow can affect the
latencies of the entire cluster (especially for queries where the slow node
was acting as a coordinator).
Is there any suggestion to avoid this behavior?
Like something on the client side to not query that bad nod
gt; https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L1000
>
> There is no equivalent to `alter system kill session`, because it is
> assumed that any query has a short, finite life in the order of seconds.
>
>
>
> On Wed, Oct 13, 2021 at 11:10 AM S G wrote:
>
I see. Thanks Jeff !
On Wed, Oct 13, 2021 at 2:25 PM Jeff Jirsa wrote:
> Convention in the yaml is default being visible commented out.
>
>
> On Wed, Oct 13, 2021 at 2:17 PM S G wrote:
>
>> ok, the link given has the value commented, so I was a bit confused.
>>
when
> that one host gets sick.
>
> The harder thing to solve is a bad coordinator node slowing down all reads
> coordinated by that node. Retry at the client level to work around that
> tends to be effective.
>
>
>
> On Wed, Oct 13, 2021 at 2:22 PM S G wrote:
>
>>
will not shoot up in proportion to server's degrading health and
hence might be very good to use.
Can someone share how big of a time-period is used to calculate the
percentile?
On Sun, Oct 17, 2021 at 1:59 PM S G wrote:
>
> "The harder thing to solve is a bad coordinator node
Hello,
We recently faced an issue recently where the read traffic on a big
Cassandra cluster shot up several times (think more than 20 times).
However, the client team denies sending any huge load and they have their
own traffic graphs to prove the same.
Assuming the client team's graphs are cor
Hello,
Is there any case where we would prefer one big giant cluster (with
multiple large tables) over several smaller clusters?
Apart from some management overhead of multiple Cassandra Clients, it seems
several smaller clusters are always better than a big one:
1. Avoids SPOF for all tables
se case / table can ruin
> everything (one bad read that generates GC hits all use cases), and
> eventually certain mechanisms/subsystems dont scale past certain points
> (e.g. schema - large schemas and large clusters are much harder than small
> schemas and small clusters)
>
>
>
&g
Jirsa wrote:
> Oh sorry - a cluster per application makes sense. Sharding within an
> application makes sense to avoid very very very large clusters (think:
> ~thousand nodes). 1 cluster per app/use case.
>
> On Fri, Nov 12, 2021 at 1:39 PM S G wrote:
>
>> Thanks Jeff.
&
25 matches
Mail list logo
