Further improvements could probably be had in the arena of node
multi-tenancy and/or arbitrary node
grouping/clustering.
Could you expand on what you mean by multi-tenancy, please? I'm curious.
--Nick.
On 29 Jul 2013, at 19:21, Dave Rawks d...@pandora.com wrote:
I'm still trying to figure
On 07/29/2013 02:20 PM, Dave Rawks wrote:
. I've never heard anybody have problems with our
serialization, but there is frequent and often confusing troubleshooting
around multicast vs unicast and the various
infrastructural/configuration tweaks to make the most out of those.
My
On 07/30/2013 02:45 AM, Nicholas Satterly wrote:
Could you expand on what you mean by multi-tenancy, please? I'm curious.
There is currently no application or other namespacing. If I have a
bunch of java apps on the same box and they are all emitting
jvm.memory.heap_usage, those metrics will
On 07/30/2013 05:53 AM, Chris Burroughs wrote:
On 07/30/2013 02:45 AM, Nicholas Satterly wrote:
Could you expand on what you mean by multi-tenancy, please? I'm curious.
There is currently no application or other namespacing. If I have a
bunch of java apps on the same box and they are all
I'm still trying to figure out what you're trying to improve here? XDR
seems like a fine, standard, lightweight serialization protocol to use.
It is already implemented and we've already got some protocol handling
for backwards compat for really old ganglia monitor clients. What is
there to
Hi,
Thanks for response.
I see there is no averseness to the idea of considering different
serialization format/protocol.
Before we have any contribution in terms of code/specifications, what would
be the ideal choice among these :
Hi,
Considering that we have better and compute efficient and binary
serialization open formats out there . How hard would it to make Ganglia
use them instead of XDR ?
Can the serialization format engines be pluggable, instead of being closely
integrated with XDR? Is it still worth continuing to
I'm curious to hear what you think is going to be more efficient,
platform agnostic and portable than XDR? ASN1 would be the only thing I
would even consider using instead, but it is arguable whether it would
be worth the pain of supporting more than one serialization format and
it certainly
I am not necessarily opposed to it if it's implemented in such a way not
to break backwards compatibility. Someone would need to contribute some
code.
Vladimir
On Fri, 26 Jul 2013, Dave Rawks wrote:
I'm curious to hear what you think is going to be more efficient,
platform agnostic and
