Hi Dan: A1: I prefer 'qmod -d queuename@hostname' to disable a node or nodes entirely (for maintenance, or whatever). Wildcards work, too, so 'qmod -d *@*' will disable the cluster, while 'qmod -d *@hostname' will disable a host, and 'qmod -d all.q@*' will disable the all.q queue. To permanently remove an exec host from the cluster, do 'qconf -de hostname_list', but I don't think that's what you're trying to accomplish.
A2: I would think so. Is the server actually 'down'? Powered off? sge_execd not running? I don't have much for you here, I'm sure someone else will. ;) Good luck! Let us know what you discover. -Hugh -----Original Message----- From: users-boun...@gridengine.org [mailto:users-boun...@gridengine.org] On Behalf Of Dan Hyatt Sent: Friday, September 05, 2014 12:14 PM To: grid engine users list Subject: [gridengine users] jobs are going to servers which I believe are not in the queue Hello, Question: I do not seem to be removing server from the queue list correctly. What is the best way to do it. Question 2: shouldn't grid engine remove servers from receiving jobs if it cannot talk to the server, such as server down? I have 3 blades, which should not be accepting jobs (OK, I am tracking using qmon)...I know go command line like I do for everything else. Why is the queue still sending jobs to the blades which are "down" But under cluster queue control "HOSTS" tab loadAvg/CPU/MemUsed/and Swap used I have dashes which I expect because they are not online. queue instances has AU under "states" which I thought indicated "not accepting jobs" One of the blades was actually removed from the all.q which is used by normal queue to schedule jobs. _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
