-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14/10/13 18:22, Joseph Farran wrote:
> Howdy.
> 
> We have several users using large job-arrays using 1-core per job
> array element.
> 
> We have a shared queue pointing to several 64-core nodes.
> 
> With the above setup, each of our 64-core nodes ends up with 64
> individual jobs from various users.   This is normal and expected
> behavior.
> 
> Is there a way to request a node such that when user A grabs say
> compute-1-1, that no other user can use that same node but allow
> user A to keep scheduling jobs to compute-1-1 as long as user A has
> 1 or more cores in use on compute-1-1?
Not easily.  As you've found out the exclusive flag grants exclusive
access on a per job rather than a per user basis.  If you make your
worker nodes admin nodes then you could associate an access list with
each node and have the prolog and epilog tweak membership thereof.  I
suspect this could be quite fragile though. You'd have to implement
something to stop grid engine from simultaneously launching two jobs
on the same node simultaneously for a start.

> 
> I tried using the complex resource:
> 
> $ qconf -se compute-1-1 hostname              compute-1-1.local 
> load_scaling          NONE complex_values    exclusive=true
> 
> $ qconf -sc | grep exclusive exclusive           excl       BOOL
> EXCL    YES YES        0        1000
> 
> 
> And requesting it via qsub with:
> 
> #$ -l exclusive=1
> 
> And it works, except that it only allows 1-core per user.     What
> is the trick to setting up the consumable so that it will allow up
> to 64 cores and only from the same user?
> 
> Joseph
> 
> _______________________________________________ users mailing list 
> [email protected] https://gridengine.org/mailman/listinfo/users
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSXQDFAAoJEKCzH4joEjNWpJgP/3+Kgg2imWg8kosJM1keqvzT
eGeWBBfoM+8vhXC15bnCX51NT2diwoWrhZEtNJuldri6bDqhyVt5lLOOHsy3+2Al
e0SOCoiFGhxbnrtuhQVu1UNQUhapnzzG49nJkDakYCb/v33Mj1R1YRmymFJ1Zjpe
iUFchZY5t4o1/3kG7k6b3zr2OiKFfZwofrAY574STIJWHFsvjNqDI4BzjYQ3R+iJ
PvHcPAZHtT7uIuELX/Uft0k5ceoVm0IEGsYvf+Ic0QXW8AqoWb9qgdfgzhRPRw9+
T0wy3ZvO0lmnUpeu+Lh2aeWqmJ5AQojx9JxfK5p+r7xIybnU6XoYlGbUAKcsvhPR
lmUEKTHNWVNRwGP9OXiYegV/Ueyj4tikWTMQIXX3H50Zvvh9TVnOfaLsyDPRGhpz
8wQZQxnKv7KwWLbZXCU5ttLqsSR2i49u23Vd1DW7w1BvSBrVi+oMktFChudZsH2x
Bc+zGpQFYvh+m94BjQYgSXzs5G4ae20M/EszWHkN0/6bT9tUUnOHUl6rPko8Xgjz
OJLyR5FrmcnPsPb0U/YojmeRsPbMZPL22UOsMeB7oJq/4qpTgXrtwC9gGRoiedpj
O37gNUR/vo89HGxwGDo/E7RtPBJ4/IMZTLPcdpWi5C5Ahccf/z6PEU6EFtbzfD66
vSdHCc+qyT9VE/RG6zik
=+y7O
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to