This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Skip to end of metadata
Go to start of metadata

This page is a collection of gotcha's and surprises I have come across while using the Resource Manager. If you encounter any of your own, please add them here including the errors from the logs, to people will be able to find this page via Google.

Q: Whenever I submit more jobs than the number of available nodes in nodes.xml I get the following error message: Failed to find available node for job spec : null

cas_resource0.log
INFO: Assigning job: [TestJob] to node: [cervin-7]
May 2, 2012 7:42:56 AM org.apache.oodt.cas.resource.jobqueue.JobStack addJob
INFO: Added Job: [2012-05-02T07:42:56.024-07:00] to queue
May 2, 2012 7:42:56 AM org.apache.oodt.cas.resource.scheduler.LRUScheduler run
INFO: Obtained Job: [2012-05-02T07:42:55.193-07:00] from Queue: Scheduling for execution
May 2, 2012 7:42:56 AM org.apache.oodt.cas.resource.scheduler.LRUScheduler run
WARNING: Error scheduling job: [2012-05-02T07:42:55.193-07:00]: Message: Failed to find available node for job spec : null

A: This happens when you drop nodes from the nodes.xml file and you do not drop them from the node-to-queue-mapping.xml file. It is critical to keep the list of nodes in BOTH FILES synched up.