hi Cameron, AFAIK there is no way to disable the Ganglia plugin, so you'll have to setup and run a Ganglia metadata daemon (Gmetad). I'll check that again.
Cheers, Rajith On Tue, Dec 10, 2013 at 2:53 AM, Cameron Goodale <sigep...@gmail.com> wrote: > Hey Rajith and Devs, > > I am upgrading my resource manager 0.3 to the latest version (currently > 0.7-SNAPSHOT) and I have run into the Ganglia Monitor Plugin with the > following errors: > > SEVERE: The required nodeId is not available: sneffels-11 :null > java.lang.NullPointerException > at > > org.apache.oodt.cas.resource.monitor.ganglia.GangliaResourceMonitor.getLoad(GangliaResourceMonitor.java:73) > at > > org.apache.oodt.cas.resource.monitor.AssignmentMonitor.getLoad(AssignmentMonitor.java:105) > at > > org.apache.oodt.cas.resource.scheduler.LRUScheduler.nodeAvailable(LRUScheduler.java:232) > at > > org.apache.oodt.cas.resource.scheduler.LRUScheduler.schedule(LRUScheduler.java:134) > at > > org.apache.oodt.cas.resource.scheduler.LRUScheduler.run(LRUScheduler.java:108) > at java.lang.Thread.run(Thread.java:662) > Dec 9, 2013 1:17:05 PM > org.apache.oodt.cas.resource.monitor.ganglia.GangliaResourceMonitor getLoad > SEVERE: The required nodeId is not available: kush-11 :null > java.lang.NullPointerException > at > > org.apache.oodt.cas.resource.monitor.ganglia.GangliaResourceMonitor.getLoad(GangliaResourceMonitor.java:73) > at > > org.apache.oodt.cas.resource.monitor.AssignmentMonitor.getLoad(AssignmentMonitor.java:105) > at > > org.apache.oodt.cas.resource.scheduler.LRUScheduler.nodeAvailable(LRUScheduler.java:232) > at > > org.apache.oodt.cas.resource.scheduler.LRUScheduler.schedule(LRUScheduler.java:134) > at > > org.apache.oodt.cas.resource.scheduler.LRUScheduler.run(LRUScheduler.java:108) > at java.lang.Thread.run(Thread.java:662) > > > I get this error message for all 44 of the nodes I have defined in my > nodes.xml config. > > > A couple questions: > > 1. Can I simply run resource manager without the Plugin via a change in > config? I tried to comment out the config lines, but it didn't work. > > 2. If I cannot simply disconnect the Ganglia Dependency, then do I have to > setup and run a Ganglia metadata daemon? > > > I look forward to your reply, > > > Cameron > > -- > > Sent from a Tin Can attached to a String >
