Upgrading to Sun Grid Engine 6.2 While Keeping the Old Cluster


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Upgrading to Sun Grid Engine 6.2 While Keeping the Old Cluster
# 1  
Old 12-16-2009
Upgrading to Sun Grid Engine 6.2 While Keeping the Old Cluster

A hands-on demonstration.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Sun Grid Engine (SGE) scripts - processors?

Hi, I was trying to run a program that calls 8 processors (with max. RAM of 2 GB per processor). I want to run this program on my cluster that runs SGE. The cluster has 2 nodes, and each node has 62 cores, and 248GB/node. Currently, I use the scripts below, but the program (softx below) crashes... (0 Replies)
Discussion started by: pc2001
0 Replies

2. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

3. Solaris

How to activate "high" priority queues for codine (Sun Grid Engine) under solaris 10

How to activate "high" priority queues for codine (Sun Grid Engine) under solaris 10? What are the steps? (0 Replies)
Discussion started by: ionrivera
0 Replies

4. High Performance Computing

Alternative to Sun Grid Engine

Does anybody know of a good alternative to Sun Grid Engine? It seems that Oracle is now charging for this software. I am running a HPC cluster that has Solaris 10 machines and I am adding some nodes that will be running Ubuntu 10.04, eventually the Solaris machines will be migrating to Ubuntu. (0 Replies)
Discussion started by: ccj4467
0 Replies

5. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

6. Linux

Upgrading CPU, keeping hard drive?

I assembled this computer with the idea of upgrading the guts (motherboard, CPU, and probably RAM) down the road, while keeping the optical drive, hard drive, case, and peripherals. How much trouble will this cause if I get a similar CPU? How much trouble if I get an altogether different CPU --... (5 Replies)
Discussion started by: CRGreathouse
5 Replies

7. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies
Login or Register to Ask a Question
QRDEL(1)						   Sun Grid Engine User Commands						  QRDEL(1)

NAME
qrdel - delete Sun Grid Engine Advance Reservations (AR) SYNTAX
qrdel [-f] [-help [-u wc_user_list] wc_ar_list DESCRIPTION
Qrdel provides a means for a user/operator/manager to delete one or more Advance Reservations (AR). A manager/operator can delete ARs belonging to any user, while a regular user can only delete his or her own ARs. If a manager wants to delete another user's AR, the man- ager can specify the AR id. By default, "qrdel wc_ar_name" will delete only the ARs belonging to that user. A manager is able to delete another user's AR via "-u wc_user_list". Jobs referring to an AR tagged for deletion will also be removed. Only if all jobs referring to an AR are removed from the Sun Grid Engine database will the AR also be removed. Qrdel deletes ARs in the order in which the AR identifiers are presented. Find additional information concerning wc_user_list and wc_ar_list in sge_types(1). OPTIONS
-f Force action for AR. The AR and the jobs using the AR are deleted from the Sun Grid Engine queuing system even if the sge_execd(8) controlling the AR jobs does not respond to the delete request sent by the sge_qmaster(8). Users which have neither Sun Grid Engine manager nor operator status can only use the -f option for their own ARs. -help Prints a list of all options. -u wc_user_list Deletes only those ARs which were submitted by users specified in the list of usernames. For managers, it is possible to use qrdel -u "*" to delete all ARs for all users. If a manager wants to delete a specific AR for a user, he has to specify the user and the AR id. If no AR is specified, all ARs belonging to that user are deleted. wc_ar_list A list of AR id's that should be deleted ENVIRONMENTAL VARIABLES
SGE_ROOT Specifies the location of the Sun Grid Engine standard configuration files. SGE_CELL If set, specifies the default Sun Grid Engine cell. To address a Sun Grid Engine cell qrdel uses (in the order of prece- dence): The name of the cell specified in the environment variable SGE_CELL, if it is set. The name of the default cell, i.e. default. SGE_DEBUG_LEVEL If set, specifies that debug information should be written to stderr. In addition the level of detail in which debug infor- mation is generated is defined. SGE_QMASTER_PORT If set, specifies the tcp port on which the sge_qmaster(8) is expected to listen for communication requests. Most installa- tions will use a service map entry for the service "sge_qmaster" instead of defining the port. FILES
<sge_root>/<cell>/common/act_qmaster Sun Grid Engine master host file SEE ALSO
sge_intro(1), qrstat(1), qrsub(1), qsub(1), sge_qmaster(8), sge_execd(8). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ QRDEL(1)