No. Each agent is responsible for collecting and reporting all the
statistics for the node it is installed on, so there shouldn't be any
duplication.
On Sat, Mar 31, 2012 at 5:01 AM, R. Verlangen wrote:
> Nick, would that also result in useless duplicates of the statistics?
>
>
> 2012/3/30 Nick B
Nick, would that also result in useless duplicates of the statistics?
2012/3/30 Nick Bailey
> Unfortunately at the moment OpsCenter only really supports having one
> instance per cluster. It may be possible to set up an instance in each
> datacenter, however it has not been tested and each opsce
Unfortunately at the moment OpsCenter only really supports having one
instance per cluster. It may be possible to set up an instance in each
datacenter, however it has not been tested and each opscenter instance
would lose some functionality.
On Fri, Mar 30, 2012 at 3:13 AM, Alexandru Sicoe wrote
Hi Nick,
I forgot to say I was using 1.2.3 which I think uses different ports. So I
will upgrade to 1.4.1 and open those ports across the firewall although
that's kind of a pain. I already have about 320 config lines for the
Cassandra cluster itself.
So, just to make things clear, is it mandatory
This setup may be possible although there are a few potential issues.
Firstly, see:
http://www.datastax.com/docs/opscenter/configure_opscenter#configuring-firewall-port-access
Basically the agents and OpsCenter communicate on ports 61620 and
61621 by default (those can be configured though). The
Hello,
I am planning on testing OpsCenter to see how it can monitor a multi DC
cluster. There are 2 DCs each on a different side of a firewall. I've
configured NAT on the firewall to allow the communication between all
Cassandra nodes on ports 7000, 7199 and 9160. The cluster works fine.
However w
