Hadoop plugin questions; JMX
Elias Ross
genman at noderunner.net
Thu Oct 20 17:57:00 UTC 2011
On Thu, Oct 20, 2011 at 5:18 AM, Heiko W.Rupp <hrupp at redhat.com> wrote:
> I think the main reason for me to write it the way it is was to have a
> "hadoop" server top-level resource with the various stuff below it and
> not having a dozen resources scattered around the resource tree
There's really only a few MBeans per Hadoop instance. So I don't know
if you would necessarily have a dozen or so resources?
Still, I think the hierarchy I would go with would go from:
<plugin name="hadoop">
<server name="Hadoop" discovery="HadoopDiscovery" class="HadoopComponent">
<service name="NameNode" discovery="HadoopServiceDiscovery"
class="HadoopServiceComponent">
to:
<plugin name="hadoop">
<server name="Hadoop" discovery="JMXDiscoveryComponent"
class="JMXServerComponent">
<server name="Hadoop Name Node">
<service name="FSNamesystemState" >
<service name="NameNodeActivity" >
Still, I think would be nice to group them all together. Is it
possible to nest servers like this? How can I use process scanning in
conjunction with the JMX discovery process?
> You could tweak the pluginGen plugin generator to not get its input
> from command line / stdin, but from going out to jmx and reading
> objects that match an objectname query. And then use the
> existing templating to create the artifacts.
I might do that. I might just work on the part to generate the XML
itself and stop there :-)
More information about the rhq-devel
mailing list