|
Home | Switchboard | Unix Administration | Red Hat | TCP/IP Networks | Neoliberalism | Toxic Managers |
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix |
|
|
When threshold is exceeded, no new jobs are placed on host. Essentially it is the signal that the host is busy as determined by uptime
Can use iether built-in values or values reported by custom load sensors (example: ‘logged-in-users=5’).
Default value
np_load_avg=1.75
lead to oversubscription of computational tasks. In many cases lower threshold such as 0.75 might be better.
Similar to load_threshold but running jobs will actually be suspended/stopped. The ‘nsuspend’ param determines how many jobs per interval get suspend signals.
‘suspend_interval’ defaults to 00:05:00.
What parallel environment (PE) objects this queue supports. See SGE Parallel Environment
It an be defined iether:
slots 20
slots 1,[b08=4],[b09=4]
In the latter case, the first number (1 in the example above) is the default allocation of slots, if number of slots that is assigned to the job, if number of slot is not explicitly requested in qsub command.
Numbers for each host specify maximum number of slots available on the particular host.
Trivial epilog usage:
#!/bin/sh # Simple epilog script JOB_EXIT_STATUS="`sed -ne 's/^exit_status=//p'\ $SGE_JOB_SPOOL_DIR/usage | tail -1`" echo "--------" echo "Job exited code: $JOB_EXIT_STATUS" echo "--------"
Trivial epilog usage - II … STARVEDETECT="`grep -c "Licensed number of users already reached” \ $SGE_O_WORKDIR/*.log `" if [ $STARVEDETECT -gt 0 ] then echo "License Error Pattern Detected in Output!" /bin/tcsh -c "cd $SGE_O_WORKDIR; \ /cl/sw/bin/restart-failed-job.pl " else echo "No problems detected" fi …
How to configure different prolog scripts for different hosts or host groups (2014-03-03)Daniel's Blog about Grid Engine
When configuring Grid Engine a good tuning point is always to reduce the amount of queues (i.e. queue instances). When having a need for different machine type specific prolog and epilog scripts (for different heath-check for example) this does not require to configure multiple queues containing different prolog and epilog scripts. Instead you can configure them in the same queue using the bracket notation where you can define settings for queue instances (a queue setting for a host) and queue domains (a queue setting for a hostgroup).
I‘ve configured two additional host groups: @centos and @suse11 for which I want to have different prolog scripts running before a job is started.
qconf -shgrpl @allhosts @centos @suse11
My prolog scripts just printing out something on stdout.
cat /nfs/prolog_cent.sh #!/bin/sh echo "I'm a CentOS box"
cat /nfs/prolog_suse.sh #!/bin/sh echo "I'm a SUSE box"
Now we can add those two prolog scripts in the prolog configuration of one queue. Here for the host-group @centos the /nfs/prolog_cent.sh script is set. The prolog for host-group @suse11 is set respectively(of course you can also just use an host name instead of a hostgroup).
qconf -mattr queue prolog "NONE,[@centos=/nfs/prolog_cent.sh],[@suse11=/nfs/prolog_suse.sh]" all.q daniel@mint14 modified "all.q" in cluster queue list
Now verify that the queue configuration was set in the right way.
qconf -sq all.q | grep prolog prolog NONE,[@centos=/nfs prolog_cent.sh], \ [@suse11=/nfs/prolog_suse.sh]
Finally we submit two jobs to two different hostgroups (i.e. here queue domains since the job is required to run in all.q).
qsub -b y -q all.q@@suse11 /bin/sleep 0 Your job 8 ("sleep") has been submitted qsub -b y -q all.q@@centos /bin/sleep 0 Your job 9 ("sleep") has been submitted
Now check the job output file. It must contain the prolog output.
cat /home/daniel/sleep.o9 I'm a CentOS box cat /home/daniel/sleep.o8 I'm a SUSE box
|
Switchboard | ||||
Latest | |||||
Past week | |||||
Past month |
2014-03-03 | Daniel's Blog about Grid Engine
When configuring Grid Engine a good tuning point is always to reduce the amount of queues (i.e. queue instances). When having a need for different machine type specific prolog and epilog scripts (for different heath-check for example) this does not require to configure multiple queues containing different prolog and epilog scripts. Instead you can configure them in the same queue using the bracket notation where you can define settings for queue instances (a queue setting for a host) and queue domains (a queue setting for a hostgroup).
Here is an example of how to configure different prolog scripts for different host groupsI've configured two additional host groups: @centos and @suse11 for which I want to have different prolog scripts running before a job is started.
qconf -shgrpl @allhosts @centos @suse11My prolog scripts just printing out something on stdout.
cat /nfs/prolog_cent.sh #!/bin/sh echo "I'm a CentOS box" cat /nfs/prolog_suse.sh #!/bin/sh echo "I'm a SUSE box"Now we can add those two prolog scripts in the prolog configuration of one queue. Here for the host-group @centos the /nfs/prolog_cent.sh script is set. The prolog for host-group @suse11 is set respectively (of course you can also just use an host name instead of a hostgroup).
qconf -mattr queue prolog "NONE,[@centos=/nfs/prolog_cent.sh],[@suse11=/nfs/prolog_suse.sh]" all.q daniel@mint14 modified "all.q" in cluster queue listNow verify that the queue configuration was set in the right way.
qconf -sq all.q | grep prolog prolog NONE,[@centos=/nfs prolog_cent.sh], \ [@suse11=/nfs/prolog_suse.sh]Finally we submit two jobs to two different hostgroups (i.e. here queue domains since the job is required to run in all.q).
qsub -b y -q all.q@@suse11 /bin/sleep 0 Your job 8 ("sleep") has been submitted qsub -b y -q all.q@@centos /bin/sleep 0 Your job 9 ("sleep") has been submittedNow check the job output file. It must contain the prolog output.
cat /home/daniel/sleep.o9 I'm a CentOS box cat /home/daniel/sleep.o8 I'm a SUSE box
Google matched content |
Society
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
Quotes
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
Classic books:
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|
You can use PayPal to to buy a cup of coffee for authors of this site |
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.
Last modified: March, 12, 2019