[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Windows 2000 Server + Condor
- Date: Mon, 23 Apr 2007 09:05:37 -0700
- From: Andrew Cunningham <andrewc@xxxxxxx>
- Subject: Re: [Condor-users] Windows 2000 Server + Condor
It turned out that the problem seemed to be due to having 'hyper-
threading' on with a Pentium 4 CPU on the W2KServer - so that Condor
saw two vm's. vm1 would execute , but vm2 would fail to execute with
an error. Turning off HT solved the problems.
On Apr 23, 2007, at 2:46 AM, Matt Hope wrote:
On 4/21/07, Andrew Cunningham <andrewc@xxxxxxx> wrote:
There was some old references when googling "Condor
Condor was incompatible with Windows 2000 Server - I have had some
issues with using a Windows 2000 Server with certain jobs hanging.
Are there any known issues with W2K server + condor?
I don't know of any issues but our farm's execute nodes used XP until
win 2003 server came out and was deemed stable (the central manager
was running 2000 server but not for long, it was upgraded well before
the execute nodes).
Unless cost is a factor I would urge going to 2003 server. It has
several internal improvements, notably NUMA support (which makes a big
difference for multi socket opteron systems).
The minor hassle of tweaking a few permissions (2003 server has much
stricter default permissions) is well worth it.
You of course may have no control over this, in which case someone
else here might have experience with condor on Windows 2000 Server....