Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're replacing a home-grown queueing system with SGE/OGE. The current work environment has engineers using their own local Linux workstation to submit jobs. So I'm wondering about adding many machines as submit hosts to an SGE/OGE cluster. In our case, there would probably be on the order of 100-200 submit hosts submitting jobs to a cluster that has approximately 30-50 execution nodes.

I think that's backward from what is "normal" where there is a single submit host (or maybe just a couple) which serves as the front-end to the cluster. Are there any down-sides to having lots of submit hosts (other than having to add them via qconf)?

share|improve this question
up vote 4 down vote accepted

If there are any downsides other than keeping track of which hosts are submit hosts, I haven't seen them. To the best of my knowledge, GridEngine only ever checks the list at submission time and never initiates any connections from the server to the submit hosts.

In our environment all our workstations, exec hosts, and a number of other machines are set up as submit hosts and thus far I have not seen any detrimental effects as a result. The total count is around 120.

We allow job submission from user workstations as well as having a gateway machine that can be accessed via SSH for VPN users.

share|improve this answer
Thanks - nice tip about the gateway machine for remote users. – Rick Reynolds Oct 14 '11 at 14:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.