Hi William, Am 19.04.2012 um 11:25 schrieb William Hay:
> As I mentioned in a previous e-mail we had a planned outage recently > and our grid engine config was corrupted when we tried to restart due > to filesystem problems. > > We managed to restore the grid engine config from backup while > retaining all the queued jobs. But before allowing them on we wanted > to test the system. > > To facilitate this I used qconf -mconf and set projects to a project > that only the system administration team were members of. > > Despite this when we powered on the worker nodes lots of regular user > jobs started on the nodes as they come up (we have initial_state > enabled on all our queues). > > Is this a known bug or have I misunderstood the use of the projects > setting in sge_conf (it occurs to me it might only control job > submission not running)? on the top level I would expect it to work for submissions only (as it is described in `man sge_conf`). For queues/exechosts it is for scheduling. Therefore the exechost setting can't override the global setting as both are in effect. If you would have set it for queues/hosts you should haven gotten the desired behavior. It might be a matter of discussion would should happen to already submited jobs. With the actual implementation you have the option to drain a project to remove it finally. -- Reuti > Still using 6.2u3. > > William > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
