the most common kind of read in most uses of Cassandra).
CheersBen
On Tue, 20 Sep 2016 at 15:18 Jun Wu wrote:
Yes, I think for my case, at least two nodes need to be contacted to get the
full set of data.
But another thing comes up about dynamic snitch. It's the wrapped snitch and
en
e
> other node to satisfy the query.
>
> Cheers
> Ben
>
>> On Tue, 20 Sep 2016 at 14:50 Jun Wu wrote:
>> Hi Ben,
>>
>> Thanks for the quick response.
>>
>> It's clear about the example for single row/partition. However, normally
>
on will be contained
entirely on a single node. To read the full set of data, reads would hit at
least two nodes (in practice, reads would likely end up being distributed
across all the nodes in your cluster).
CheersBen
On Tue, 20 Sep 2016 at 14:09 Jun Wu wrote:
Hi there,
I have a question
Hi there,
I have a question about the replica and replication factor.
For example, I have a cluster of 6 nodes in the same data center.
Replication factor RF is set to 3 and the consistency level is default 1.
According to this calculator http://www.ecyrd.com/cassandracalculator/, every
trace (`TRACING ON` in cqlsh) can give you a lot of the
information for an individual request. There has been a ticket to track time in
queue (https://issues.apache.org/jira/browse/CASSANDRA-8398) but no ones worked
on it yet.
Chris
On Tue, Aug 30, 2016 at 12:20 PM, Jun Wu wrote:
Hi
gards,Matija
On Tue, Aug 30, 2016 at 7:20 PM, Jun Wu wrote:
Hi there,
I'm very interested in the read/write path of Cassandra. Specifically, I'd
like to know the whole process when a read/write request comes in.
I noticed that for reach request it could go through multiple
Hi there,
I'm very interested in the read/write path of Cassandra. Specifically, I'd
like to know the whole process when a read/write request comes in.
I noticed that for reach request it could go through multiple stages. For
example, for read request, it could be in ReadStage, RequestR
Hi there,
I have a question for dynamic snitch, specifically in reading.
For dynamic snitch, it is wrapped with other snitches. For reading, dynamic
snitch plays a very important role, as mentioned in this article:
http://www.datastax.com/dev/blog/dynamic-snitching-in-cassandra-past-pres
for monitoring Cassandra:
https://sematext.com/spm/integrations/cassandra-monitoring/Otis
--
Monitoring - Log Management - Alerting - Anomaly DetectionSolr & Elasticsearch
Consulting Support Training - http://sematext.com/
On Mon, Jun 13, 2016 at 5:17 PM, Jun Wu wrote:
Hi there,
I
Hi there,
I've deployed 6 node in Amazon EC2. I'm trying to monitor some metrics for
each node and print them out when I write/read data into Cassandra.
Specifically I want to print out the information about garbage collection and
compaction.
I do notice that there's metrics for compaction
I've worked on some experiments with AWS EC2. According to the doc you provided
and from my own experience, EC2Multiregionsnitich should be the right setting
as you have 2 different datacenters.
In cassandra.yaml: change seeds to public address list, change listen and rpc
address to private addr
a big part of the 2.1
> release, but I'm not sure if the change in coordinators was part of that
> effort or not.
>
> Steve
>
>
> On Fri, Jan 29, 2016 at 10:13 AM, Jun Wu <mailto:wuxiaomi...@hotmail.com>> wrote:
> Hi Steve,
>
>Thank you so much fo
ou would end up duplicating what is already being
done for you internally.
Steve
On Fri, Jan 29, 2016 at 9:11 AM, Jun Wu wrote:
Hi there,
I have some questions about the replicas selection.
Let's say that we have 2 data centers: DC1 and DC2, the figure also be got
from link
Hi there,
I have some questions about the replicas selection.
Let's say that we have 2 data centers: DC1 and DC2, the figure also be got
from link here:
https://docs.datastax.com/en/cassandra/1.2/cassandra/images/write_access_multidc_12.png.
There're 10 nodes in each data center. We set
14 matches
Mail list logo
