On 6 December 2011 10:21, Reuti <[email protected]> wrote: > Hi, > > Am 04.12.2011 um 11:57 schrieb mahbube rustaee: > >> I defined an exclusive tag in complex resources for users that can request >> "-l excl=1 " >> Such users, lock free slots of hosts that have added excl=true to >> consumable resources. >> >> 1) In this case, how can I get accounting for all of slots that a user cause >> to lock on hosts? > > it's not recorded in the accounting file where the job ran, i.e. a > "pe_hostfile" like record. As a result also the blocked slots are not > recorded. What you can try if you need it: use a global (or queue) prolog, > which runs under e.g. the sgeadmin account by prefixing it with the name (see > `man queue_conf`, resp. `man sge_conf`) and copy the "pe_hostfile" with the > information of the distribution to a central place. Whether the exclusive > access was requested, is recorded already in the accounting file (like all -l > resource requests). > > With this information, you can compute the real blocked cores then. > > -- Reuti > > NB: although the exclusive attribute is often attached to exechosts, it can > also be attached to queues (i.e. exclusive access to queue instances). But as > you know how your cluster was set up, you can set it up in the correct way in > your processing of the "pe_hostfile" then to honot the blocked slots > correctly.
A trick we use here is to have the JSV calculate the slots that would be blocked by the job and stuff this into the account string. This causes issues with soft requests so at the moment we have the JSV stomp on them. As they have a nasty effect on scheduler performance this is no bad thing. William _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
