>
>> Writes are atomic – it depends on your chosen consistency
>> level to determine if writes will fail or succeed.
>>
>>
>>
>> *From:* Павел Сапежко [mailto:amelius0...@gmail.com]
>> *Sent:* Friday, July 07, 2017 8:23 AM
>> *To:
– it depends on your chosen consistency
> level to determine if writes will fail or succeed.
>
>
>
> *From:* Павел Сапежко [mailto:amelius0...@gmail.com]
> *Sent:* Friday, July 07, 2017 8:23 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Understanding of cassandra metrics
[mailto:amelius0...@gmail.com]
Sent: Friday, July 07, 2017 8:23 AM
To: user@cassandra.apache.org
Subject: Re: Understanding of cassandra metrics
Are you really think that I don't read docs? Do you have enough information in
the documentation? I think no. What exactly does mean CoordinatorScanLatency
Are you really think that I don't read docs? Do you have enough information
in the documentation? I think no. What exactly does mean CoordinatorScanLatency
for example? Is it latency on full table scan or maybe range scan by
clustering key? What exactly mean ViewLockAcquireTime? What is "partition
1st result on google returns:
http://cassandra.apache.org/doc/latest/operating/metrics.html
On Fri, Jul 7, 2017 at 12:16 PM, Павел Сапежко
wrote:
> Hello, I have several question about cassandra metrics. What does exactly
> mean the next metrics:
>
>-
Hello, I have several question about cassandra metrics. What does exactly
mean the next metrics:
- CoordinatorReadLatency
- CoordinatorScanLatency
- ReadLatency
- RangeLatency
- ViewLockAcquireTime
- ViewReadTime
--
С уважением,
Павел Сапежко
skype: p.sapezhko