Hi,
Looks like you need a monitoring for Cassandra but without using JMX.
It is possible to use metric reporting libraries in Cassandra:
https://wiki.apache.org/cassandra/Metrics#Reporting
I do not have specific experience with using Cassandra on DCOS but,
monitoring with libraries and tools
Akshay,
avoid running repair in that case, it'll take way longer than rebuild and
it will stream data back to your original DC, even between nodes in that
original DC, which is not what you're running after, and could lead to all
sorts of troubles.
Run "nodetool rebuild " as recommended by Jon
Repair will take way more time then rebuild.
On Wed, Oct 31, 2018 at 6:45 AM Kiran mk wrote:
> Run the repair with -pr option on each node which will repair only the
>
> parition range.
>
>
>
> nodetool repair -pr
>
> On Wed, Oct 31, 2018 at 7:04 PM Surbhi Gupta
> wrote:
>
> >
>
> > Nodetool
Run the repair with -pr option on each node which will repair only the
parition range.
nodetool repair -pr
On Wed, Oct 31, 2018 at 7:04 PM Surbhi Gupta wrote:
>
> Nodetool repair will take way more time than nodetool rebuild.
> How much data u have in your original data center?
> Repair should
Nodetool repair will take way more time than nodetool rebuild.
How much data u have in your original data center?
Repair should be run to make the data consistent in case of node down more
than hintedhandoff period and dropped mutations.
But as a thumb rule ,generally we run repair using opscenter
Hello All,
have someone experience with monitoring cassandra in DCOS?
If we increase the load to the Casandra in DCOS, the application get timeouts
and loose the connection and I do not have any information about what happened.
Is there a way to get information about the amount of current
Hi Jonathan,
That makes sense. Thank you for the explanation.
Another quick question, as the cluster is still operative and the data for
the past 2 weeks (since updating replication factor) is present in both the
data centres, should I run "nodetool rebuild" or "nodetool repair"?
I read that
Pretty cool!
Dinesh
> On Oct 30, 2018, at 6:31 PM, Jonathan Haddad wrote:
>
> Very cool Ben, thanks for sharing!
>
>> On Tue, Oct 30, 2018 at 6:14 PM Ben Slater
>> wrote:
>> For anyone who is interested, we’ve published a blog with some more
>> background on this and some more detail of
