Thank you
On Fri, Sep 18, 2020 at 4:59 PM Erick Ramirez
wrote:
> For the metrics
>> "org.apache.cassandra.metrics:name=[DC]-Latency,type=Messaging" which is
>> the unit of the metrics?
>>
>
> They're in milliseconds:
>
> timer.update(timeTaken, TimeUnit.MILLISECONDS);
> crossNode
>
> For the metrics
> "org.apache.cassandra.metrics:name=[DC]-Latency,type=Messaging" which is
> the unit of the metrics?
>
They're in milliseconds:
timer.update(timeTaken, TimeUnit.MILLISECONDS);
crossNodeLatency.update(timeTaken, TimeUnit.MILLISECONDS);
See
https://github.com/a
Hello,
For the metrics
"org.apache.cassandra.metrics:name=[DC]-Latency,type=Messaging" which is
the unit of the metrics?
-b -i -q 75thPercentile
999thPercentile DurationUnitMax Min
StdDev
-d
(https://www.cloudping.co/ is a useful place to get inter-region latency in
AWS)
On Tue, Oct 17, 2017 at 9:20 PM, Chris Lohfink wrote:
> An alternative if using >3.8 you can use the org.apache.cassandra.
> metrics:type=Messaging,name=[DC]-Latency mbean where [DC] is the name of
> the DC and you
An alternative if using >3.8 you can use the
org.apache.cassandra.metrics:type=Messaging,name=[DC]-Latency mbean where
[DC] is the name of the DC and you can get the inter DC latency per node
(to that node). This does not account for NTP drift though, just how long
it takes messages (ie mutations)
I recommend figuring out the latency between your datacenters. Cassandra isn’t
going to be any more than that barring JVM pauses on the remote coordinator.
> On Oct 17, 2017, at 4:17 PM, Bill Walters wrote:
>
> Hi Everyone,
>
> I need some suggestions on finding the time taken for Cassandra r
Hi Everyone,
I need some suggestions on finding the time taken for Cassandra replication
to happen from east to west region for write and read operations on a multi
DC cluster.
Currently, below is our cluster setup.
*Cassandra version:* DSE 5.0.7
*No of Data centers:* 2 (AWS East and AWS West reg
