@Rob - You can have OpsCenter not write to the cluster it's monitoring: http://www.datastax.com/dev/blog/storing-opscenter-data-in-a-separate-cluster.
OpsCenter has supported this for sometime. On 26 Aug 2014, at 12:07, Mark Reddy <mark.l.re...@gmail.com> wrote: >> Why is there so much OpsCenter work happening? > > Opscenter stores a lot of information regarding all aspects of your cluster, > such as OS, cluster, keyspace and individual table metrics, after a set > period of time these granular data point are rolled up into aggregates. This > is what you are seeing in the logs. > >> Is there a way to disable it > > Yes, you could stop monitoring your cluster with OpsCenter or store less > granular data, see the docs for all the options to can tune: > http://www.datastax.com/documentation/opscenter/5.0/opsc/configure/opscConfigureDataCollectionExpiration_c.html > >> and whats the impact > > The only impact is that you will either have less granular metric data to > work with or none at all (from OpsCenter) > > > Mark > > Regards, > Mark > > >> On 25 August 2014 22:35, Robert Coli <rc...@eventbrite.com> wrote: >>> On Mon, Aug 25, 2014 at 1:42 PM, Ruchir Jha <ruchir....@gmail.com> wrote: >>> I see a lot of activity around the OpsCenter_rollups CFs in the logs. Why >>> is there so much OpsCenter work happening? Is there a way to disable it, >>> and whats the impact? >> >> Opscenter is tracking the metrics for your cluster and storing the tracking >> data... in your cluster. This would generally seem to not make a whole lot >> of sense, but there you have it. >> >> There is probably a way to disable the stats collection part of OpsCenter, >> but that's presumably part of the value add of OpsCenter. >> >> =Rob >
