Jobs being killed on Condor Enviroment

I am running an executable in Condor that basically processes an input Image and saves a binary image in a given folder. I use this code in 213 images.

My condor configuration file contents are as following:

universe     = vanilla
executable   = /datasets/me/output_cpen_database/source_codes_techniques/test/vole
arguments    = cmfd -I /datasets/me/cpen_database/scale1/$(Process)/$(Process).png -O /datasets/me/output_cpen_database/scale1/dct/$(Process)/ --numThreads 10 --chan GRAY --featvec DCT --blockSize 16 --minDistEuclidian 50 --kdsort --fastsats --minSameShift 1000 --markRegions --useOrig --writePost --writeMatrix
initialdir   = /datasets/me/output_cpen_database/source_codes_techniques/test
requirements = (OpSysAndVer == "Ubuntu12")
request_cpus   = 5
request_memory = 20000
output       = logs/output-$(Process).log
error        = logs/error-$(Process).log
log          = logs/log-$(Process).log
Notification = Complete
Notify_User =
Queue 214

Some images are processed OK, but in some cases I receive the following error in my mailbox:

Condor job 1273.47
/datasets/me/output_cpen_database/source_codes_techniques/test/vole cmfd -I /datasets/me/cpen_database/scale1/47/47.png -O    /datasets/me/output_cpen_database/scale1/dct/47/ --numThreads 10 --chan GRAY --featvec DCT --blockSize 16 --minDistEuclidian 50 --kdsort --fastsats --minSameShift 1000 --markRegions --useOrig --writePost --writeMatrix
died on signal 9 (Killed)

I was thinking if this happens because of lack of memory, but this image’s (named 47) size is not longer than 20MB (actually it has 16.7MB).

As I said before, the condor runs this executable ok for some other images .

Should I have to increase the request_memory in my configuration file? what is happening here?

Source: New Questions

Leave a Reply