Re: [HTCondor-users] move spool and log folders on high speednetwork drive

[Antonis Sergis <sergis_antonis@xxxxxxxxxxx>]

hello John,

 

many thanks for the advices! I am afraid an http server such as an S3 is beyond our scope (and budget) at the moment. We would prefer something more simple since the gear is already installed and I wouldn’t want to get the university’s network people involved at this stage. There must be a simpler way to get this done given our set up - its just a matter of changing condor’s config file to read and write the spool and log files on the network drive. So frustrating because it worked for some time and now I can’t even figure out why it doesn’t!

 

Antonis

 

From: John Lambert

Sent: Thursday, March 28, 2013 5:57 PM

To: HTCondor-Users Mail List

Subject: Re: [HTCondor-users] move spool and log folders on high speednetwork drive

 

Antonis-

 

We were planning on attempting something similar, but we think we found a better solution:

 

We use HTTP servers as our "spool" and use a modified curl plugin. We can send you the source if you'd like, but since we use S3, I'm not sure how much it would help you. Apache or nginx as your HTTP server and the curl plugin that comes with condor will definitely take a lot of load off of your submit machines.

 

Thanks,

John Lambert

On Thu, Mar 28, 2013 at 1:11 PM, Antonis Sergis <sergis_antonis@xxxxxxxxxxx> wrote:

hello. I am writing to get some more ideas regarding a problem which is becoming rather hard to tackle. I have my machine as a condor submitter and unfortunately we realised that the local disk transfer speeds for the log and spool files is too slow and limits our maximum job number. Replacing the disk with an ssd will bring another problem close which is processor speed. I have hence decided to alter the config file to be able to make the submitting machine exchanging data over our super fast connection and network storage. I had a go trying out different things for the last days. I got it to momentarily work and the number of jobs I could carry out simultaneously went up to 1200 from 300 which was the earlier limit however then the processor maxed out and cut off taking up more jobs. We are planning to split the administration job to other PCs to get the processing speed required and the max amount of jobs running. I have tried adding the network location folders for the spool and log pathnames in the configuration file:

 

######################################################################

##  Daemon-wide settings:

######################################################################

 

##  Pathnames

LOG        = \\PATHNAME\log

SPOOL        = \\PATHNAME\spool

EXECUTE        = $(LOCAL_DIR)/execute

BIN        = $(RELEASE_DIR)/bin

LIB        = $(RELEASE_DIR)/lib

INCLUDE        = $(RELEASE_DIR)/include

SBIN        = $(BIN)

LIBEXEC        = $(BIN)

 

However this does not work and the condor service is cut off and I cannot restart it or enquire about it unless I change the config file back to the initial one (i.e. local log and spool folders). I am running condor on a windows 7 machine. Replacing the memory with an SSD is not an option as the job sizes are quite large and there are no funds to do that on a large scale while the network storage can provide the speed we are after. Any ideas?

 

Cheers

 

Antonis

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

 

---

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/