Custom Query (101 matches)
Results (49 - 51 of 101)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #68 | fixed | [PATCH] Reduce the php notices a little | ramonb | felix@… |
| Description |
Running jobmonarch gave me hundreds of warnings like: [Wed Nov 05 20:58:56 2008] [error] [client 10.10.8.99] PHP Notice: Use of undefined constant VAL - assumed 'VAL' in /var/www/html/ganglia/addons/job_monarch/overview.php on line 294 This is fixed with attached patch. |
|||
| #69 | wontfix | Job information leaking over from one Ganglia cluster to another when clusters are in the same PBS queue | ramonb | renfro@… |
| Description |
At one time, I had many Torque queues: one for each group of homogeneous systems. Since I couldn't rely on my users to consistently check qstat, showq, or Ganglia before submitting a job to an queue with free CPUs rather than a queue with none, I converted my Torque settings to put all cluster systems into one queue, and use Maui partitions to keep parallel jobs on a group of homogeneous systems. This has worked out great as far as queue efficiency is concerned. Now that I'm getting Job Monarch integrated into the setup, I've noticed that active jobs in my batch queue show up in all cluster joblists and overviews, even when that particular cluster has no active jobs on its nodes. I'll try to attach screenshots, but if my users still have jobs running when you read this ticket, you can see for yourself on the live server: Ganglia knows, for example, that "ChE Compute Nodes" has 9 systems in it named ch226-11 ... ch226-19. Monarch displays those, but also displays ch226-29 and ch226-31 from the "PNGV Project Compute Nodes" cluster that had active jobs. Any cluster view where Monarch was enabled had this effect. |
|||
| #72 | worksforme | jobmond memory leak | ramonb | ramonb |
| Description |
At least in version 0.3.1 there is a memory leak present in jobmond. Have now received multiple reports of jobmond consuming multiple gigabytes of memory after a while. |
|||
