One other thing that could be done is create the starter method for the "old" queue that resubmits the job while modifying any occurrence of -q or -l q=, etc.

That is kind of an alias then but also not too different from a wrapper script.

Cheers,

Fritz

Tina Friedrich schrieb:
On 10/03/16 10:15, Reuti wrote:

Am 10.03.2016 um 10:45 schrieb William Hay <w....@ucl.ac.uk>:

On Thu, Mar 10, 2016 at 08:19:35AM +0000, sudha.penme...@wipro.com
wrote:
Hi,



Is it possible to keep an old queue name (test.q) we have deleted
already as an alias name for the newly created queue(prod.q).

I've had the same problem recently - and my first thought was along the lines of a queue alias feature. Shame it doesn't exist.

This way we could continue to work with old scripts.
Grid Engine doesn't have direct support for this AFAICT hHowever
you can rewrite the requested queue from a JSV.  Depending on where
you put the jsv you might have to add a dummy test.q to convince
grid engine to accept the queue.

I ended up deciding against a dummy queue - I created a wrapper script that does the queue name verification/rewrite and then aliased qsub to that in the cluster environment setup.

BTW: This is something I wondered about. GridEngine will check
whether the requests are allowed and known before and after the JSV
is run. This leads to exactly the situation that a dummy queue is
needed. Would there be any flaw if the internal check by GridEngine
is done only after the JSV has run? This would allow the JSV to
correct any mis-submission and/or pseudo/dummy/alias to be resolved,
being it names of queues or complexes.

Agree - it would be nice if one had a script hook for a JSV (or something along those lines) that ran before Grid Engine does the verification. Would spare me rather a lot of helpdesk calls :)

Tina


--

UnivaFritz Ferstl | CTO and Business Development, EMEA
Univa Corporation <http://www.univa.com/> | The Data Center Optimization Company
E-Mail: ffer...@univa.com | Mobile: +49.170.819.7390





_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to