Making Grid Engine Highly Available


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Making Grid Engine Highly Available
# 1  
Old 12-16-2009
Making Grid Engine Highly Available

Ashutosh Tripathi, Senior Software Engineer, Sun Microsystems, presents at the Open Source Grid & Cluster Conference, Oakland CA, May 2008

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 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. Post Here to Contact Site Administrators and Moderators

Priority one: Remove highly confidential data

Hi Kindly remove the following from the post . These are confidential info posted by mistake and there is escalation on our company side . Kindly help. Link : https://www.unix.com/shell-programming-and-scripting/194721-process-field-1-depending-field-6-a.html Terms to be removed : itf... (0 Replies)
Discussion started by: ptappeta
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
Login or Register to Ask a Question
USER(5) 						   Sun Grid Engine File Formats 						   USER(5)

NAME
user - Sun Grid Engine user entry file format DESCRIPTION
A user entry is used to store ticket and usage information on a per user basis. Maintaining user entries for all users participating in a Sun Grid Engine system is required if Sun Grid Engine is operated under a user share tree policy. If the enforce_user cluster configuration parameter is set to auto, a user object for the submitting user will be created automatically during job submission, if one does not already exist. The auto_user_oticket, auto_user_fshare, auto_user_default_project, and auto_user_delete_time cluster configuration parameters will be used as default attributes of the new user object. A list of currently configured user entries can be displayed via the qconf(1) -suserl option. The contents of each enlisted user entry can be shown via the -suser switch. The output follows the user format description. New user entries can be created and existing can be modi- fied via the -auser, -muser and -duser options to qconf(1). Note, Sun Grid Engine allows backslashes () be used to escape newline ( ewline) characters. The backslash and the newline are replaced with a space (" ") character before any interpretation. FORMAT
A user entry contains four parameters: name The user name as defined for user_name in sge_types(1). oticket The amount of override tickets currently assigned to the user. fshare The current functional share of the user. default_project The default project of the user. delete_time Note: Deprecated, may be removed in future release. The wall-clock time when this user will be deleted, expressed as the number of seconds elapsed since January 1, 1970. If set to zero, the affected user is a permanent user. If set to one, the user currently has active jobs. For additional information about automatically cre- ated users, see the enforce_user and auto_user_delete_time parameters in sge_conf(5). SEE ALSO
sge_intro(1), sge_types(1), qconf(1). sge_conf(5). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ USER(5)