something fishy about a Metrics+Ganglia integration

[Mitch Gitman]

I've inherited an integration of Cassandra's Codahale Metrics reporting
with Ganglia that looks sensible enough on the Metrics side. The
metrics-reporter-config.yaml points to a gmond.conf on the node. Excerpt:
ganglia:
  -
period: 60
timeunit: 'SECONDS'
gmondConf: '/etc/ganglia/gmond.conf'

Now if I look at the gmond.conf on one of the nodes in the Cassandra
cluster, I see that there's a UDP entry for EVERY node in the cluster, plus
OpsCenter:

udp_send_channel {
  host = sandbox-cas00
  port = 8649
  ttl = 1
}

udp_send_channel {
  host = sandbox-cas01
  port = 8649
  ttl = 1
}

udp_send_channel {
  host = sandbox-cas02
  port = 8649
  ttl = 1
}

udp_send_channel {
  host = sandbox-cas03
  port = 8649
  ttl = 1
}

udp_send_channel {
  host = sandbox-cas04
  port = 8649
  ttl = 1
}

udp_send_channel {
  host = sandbox-opscenter
  port = 8649
  ttl = 1
}

What strikes me funny about this configuration is that every node in the
cluster is referenced. I was expecting that each node's gmond.conf would
only define a udp_send_channel for itself. This is fine now with a
five-node cluster, and we have enough deployment automation in place to
mitigate the fact that every time we add a Cassandra node every other
Cassandra node's gmond.conf would have to be updated. But is it really the
intention that every Ganglia host needs to be aware of every other host? I
was expecting that it would only be the Ganglia server these hosts are
reporting to that would need to be aware of the full membership of the
cluster.

OK, I realize at this point I'm asking more of a Ganglia question than a
Cassandra or Metrics question. Apparently, we're using Ganglia in unicast
mode rather than multicast.

Re: Cassandra Java Driver

[Brice Dutheil]

Not yet. The latestest DSE (4.8.3) is shipped with a patched version of
Cassandra 2.11.
You can find this information on their website.

4.8 Release note :
https://docs.datastax.com/en/datastax_enterprise/4.8/datastax_enterprise/RNdse.html
>From this page in the menu you can navigate and unroll the menu *Product
Guide* > *Datastax Enterprise* it should contain DSE versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH
-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda <
noo...@noorul.com> wrote:

> Is DSE shipping with 3.x ?
>
> Thanks and Regards
> Noorul
>
> On Fri, Dec 25, 2015 at 9:07 PM, Alexandre Dutra
>  wrote:
> > Hi Jean,
> >
> > You should use 3.0.0-beta1.
> >
> > TL;DR
> >
> > DataStax Java driver series 2.2.x has been discontinued in favor of
> series
> > 3.x; we explained why in this mail to the Java driver mailing list. We do
> > not advise users to use this series.
> >
> > So the most recent driver version compatible with all versions of
> Cassandra,
> > including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1 will be
> > released very soon.
> >
> > In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly
> tested
> > against all versions of Cassandra and is definitely production-ready...
> as
> > long as the Cassandra version in use is also production-ready. Note
> however
> > that Cassandra 2.2 and 3.0 are quite recent and most companies AFAICT do
> not
> > consider them yet as production-ready.
> >
> > Hope that helps,
> >
> > Alexandre
> >
> >
> > On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> >  wrote:
> >>
> >> Hi,
> >> Which Java Driver is suited for Cassandra 2.2.x. ?
> >> I see datastax 3.0.0 beta1 and datastax 2.2.0 rc3...
> >> Are they suited for production?
> >> Is there anything better?
> >> Thanks for your comments and replies?
> >> Jean
> >
> > --
> > Alexandre Dutra
> > Driver & Tools Engineer @ DataStax
>