Adaptive Computing Inc - Why does TORQUE send the mom hierarchy to down nodes?

Why does TORQUE send the mom hierarchy to down nodes?

Issue: Why does TORQUE send the mom hierarchy to down nodes?

I have 6 node (out of 590) that are marked down and/or offline.

I have 5000+ messages in my server logs complaining that it couldn't connect and/or send the mom hierarchy to these nodes.

Shouldn't the server be intelligent enough to realize that these nodes (especially the ones marked "down") aren't available for such communication?

Solution:

This has been fixed. Please upgrade to5.1.3, 6.0.2.

Tags: mom hierarchy

Last update:: 2016-08-08 19:04
Author:: Jason Booth
Revision:: 1.0

Most popular FAQs

Can I create administrative reservation for floating licenses? (33492 views)
Why does Moab append a qos from the IDCFG ... (32883 views)
How will Moab act if I add and over ... (32115 views)
How do NODEAVAILABILITYPOLICY and NODEALLOCATIONPOLICY work? (31783 views)
Why does Moab misinterpret the hostlist from Torque, reserving ... (31591 views)
Moab/TORQUE is reporting a job that is no longer ... (26207 views)
Why does my job run on only 1 node? ... (26032 views)
Why will my job not start when there is ... (25797 views)
How to get all cgroup cpuset cores with singlejob ... (25538 views)
My job exited with a code and I do ... (25394 views)

Latest FAQs

What are the fields in the events statistics files? ... (2024-06-14 15:28)
How do I use checkjob to diagnose job issues? ... (2022-09-13 16:56)
What are the meanings of the fields returned by ... (2022-06-24 18:18)
Why do I have incorrect job charges in Moab ... (2022-06-24 16:27)
How do I increase the stack size for my ... (2022-02-01 20:17)