 |
|
|
| Main Page |
| 4.1 What is the standard universe? |
| 4.2 Linking a program for standard universe |
| 4.3 Submitting a standard universe program |
| 4.4 Advanced tricks in the standard universe |
4.0 Submitting a standard universe job
4.1 What is the standard universe?
Your first job was considered a vanilla universe job. This meant that it was a plain old job. Condor also supports standard universe jobs. If you have the source code for your program and if it meets certain requirements, you can re-link your program and Condor will provide two major features for you:
- Your job can be checkpointed and restarted. When a job is checkpointed, its complete state is saved. When it is restarted, it restarts from where it was checkpointed. If your job is checkpointed periodically, you can recover if there is some sort of failure or interruption. This is incredibly useful for long-running jobs--wouldn't you hate to lose hours or days of work due to a power outage? When Condor restarts, it can restart your job from the last checkpoint, saving you lots of time.
- Your job can use remote I/O. This means that every file operation the job makes is performed on the submission computer, so it appears as though the job is running on the submission computer, not the execution computer. If you have files that are not on a shared filesystem, this can be very useful.
Your tutorial leader will give you more details about standard universe, or you can read about them online.
4.2 Linking a program for standard universe
First, you need a job to run. We'll use the same job as before. In case you don't have it, here it is. Save it in simple.c:
#include <stdio.h>
main(int argc, char **argv)
{
int sleep_time;
int input;
int failure;
if (argc != 3) {
printf("Usage: simple <sleep-time> <integer>\n");
failure = 1;
} else {
sleep_time = atoi(argv[1]);
input = atoi(argv[2]);
printf("Thinking really hard for %d seconds...\n", sleep_time);
sleep(sleep_time);
printf("We calculated: %d\n", input * 2);
failure = 0;
}
return failure;
}
Now compile the program using condor_compile. This doesn't change how the program is compiled, just how it is linked. Take note that the executable is named differently.
% condor_compile gcc -o simple.std simple.c LINKING FOR CONDOR : /usr/bin/ld -L/usr/local/condor/lib -Bstatic --eh-frame-hdr -m elf_i386 -dynamic-linker /lib/ld-linux.so.2 -o simple.std /usr/local/condor/lib/condor_rt0.o /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../crti.o /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/crtbeginT.o -L/usr/local/condor/lib -L/usr/lib/gcc-lib/i386-redhat-linux/3.2.3 -L/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../.. /tmp/ccw0wknf.o /usr/local/condor/lib/libcondorzsyscall.a /usr/local/condor/lib/libcondor_z.a /usr/local/condor/lib/libcomp_libstdc++.a /usr/local/condor/lib/libcomp_libgcc.a /usr/local/condor/lib/libcomp_libgcc_eh.a /usr/local/condor/lib/libcomp_libgcc_eh.a -lcondor_c -lcondor_nss_files -lcondor_nss_dns -lcondor_resolv -lcondor_c -lcondor_nss_files -lcondor_nss_dns -lcondor_resolv -lcondor_c /usr/local/condor/lib/libcomp_libgcc.a /usr/local/condor/lib/libcomp_libgcc_eh.a /usr/local/condor/lib/libcomp_libgcc_eh.a /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/crtend.o /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../crtn.o /usr/local/condor/lib/libcondorzsyscall.a(condor_file_agent.o)(.text+0x250): In function `CondorFileAgent::open(char const*, int, int)': /home/condor/execute/dir_1234/userdir/src/condor_ckpt/condor_file_agent.C:99: the use of `tmpnam' is dangerous, better use `mkstemp' /usr/local/condor/lib/libcondorzsyscall.a(switches.o)(.text+0x5fc5): In function `__gets_chk': /home/condor/execute/dir_1234/userdir/src/condor_syscall_lib/switches.remap-LINUX.h:435: the `gets' function is dangerous and should not be used. % ls -lh simple.std -rwxr-xr-x 1 aroy users 12M Jan 30 16:49 simple.std
There are a lot of warnings there--you can safely ignore those warnings. You can also see just how many libraries we link the program against. It's a lot! And yes, the executable is much bigger now. Partly that's the price of having checkpointing and partly it is because the program is now statically linked, but you can make it slightly smaller if you want by getting rid of debugging symbols:
% strip simple.std % ls -lh simple.std -rwxr-xr-x 1 aroy users 1.1M Jan 30 16:53 simple.std
Note the extra output when you run the program by hand now:
% ./simple.std 4 10 Condor: Notice: Will checkpoint to ./simple.std.ckpt Condor: Notice: Remote system calls disabled. Thinking really hard for 4 seconds... We calculated: 20
4.3 Submitting a standard universe program
Submitting a standard universe job is almost the same as a vanilla universe job. Just change the universe to standard. Here is a sample submit file. I suggest making it run for a longer time, so we can experiment with the checkpointing while it runs. Also, get rid of the multiple queue commands that we had. Here is the complete submit file, I suggest naming it submit.std.
Universe = standard Executable = simple.std Arguments = 120 10 Log = simple.log Output = simple.out Error = simple.error Queue
Notice that we are not transferring files this time. This is because standard universe provides remote I/O: all I/O for a job behaves as if it actually is being performed at the submission computer. This is convenient for complex jobs that access lots of files on the file system including shared libraries, input, and output.
Then submit it as you did before, with condor_submit:
% rm simple.log
% condor_submit submit.std
Submitting job(s).
Logging submit event(s).
1 job(s) submitted to cluster 45031.
% condor_q
-- Submitter: osg-edu.cs.wisc.edu : <192.168.0.1:32775> : osg-edu.cs.wisc.edu
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
45031.0 roy 4/28 16:27 0+00:00:00 I 0 9.8 simple.std 120 10
1 jobs; 1 idle, 0 running, 0 held
-- Submitter: osg-edu.cs.wisc.edu : <192.168.0.1:32775> : osg-edu.cs.wisc.edu
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
45031.0 roy 4/28 16:27 0+00:00:12 R 0 9.8 simple.std 120 10
1 jobs; 0 idle, 1 running, 0 held
-- Submitter: osg-edu.cs.wisc.edu : <192.168.0.1:32775> : osg-edu.cs.wisc.edu
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
0 jobs; 0 idle, 1 running, 0 held
% cat simple.log
000 (45031.000.000) 04/28 16:27:57 Job submitted from host: <192.168.0.1:32775>
...
001 (45031.000.000) 04/28 16:28:07 Job executing on host: <192.168.0.4:33478>
...
005 (45031.000.000) 04/28 16:28:44 Job terminated.
(1) Normal termination (return value 0)
Usr 0 00:00:00, Sys 0 00:00:00 - Run Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Run Local Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Total Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Total Local Usage
1035 - Run Bytes Sent By Job
1137886 - Run Bytes Received By Job
1035 - Total Bytes Sent By Job
1137886 - Total Bytes Received By Job
Notice that the log file has a bit more information this time: we can see how much data was transfered to and from the job because it's in the standard universe. The remote usage was not very interesting because the job just slept, but a real job would have some interesting numbers there.
4.4 Advanced tricks in the standard universe
At this point in the tutorial, I will demonstrate how you can force your job to be checkpointed and what it will look like. We will use a command called condor_checkpoint that you normally never to use, so we can demonstrate. One reason that it normally isn't used is because it checkpoints all jobs running on a computer, not just the job you want to checkpoint. Be warned.
Begin by submitting your job, and figuring out where it is running:
% rm simple.log % condor_submit submit.std Submitting job(s). Logging submit event(s). 1 job(s) submitted to cluster 45031. % condor_q -- Submitter: osg-edu.cs.wisc.edu : <192.168.0.1:32775> : osg-edu.cs.wisc.edu ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD 45031.0 roy 4/28 16:27 0+00:00:12 R 0 9.8 simple.std 120 10 1 jobs; 0 idle, 1 running, 0 held % condor_q -run -- Submitter: osg-edu.cs.wisc.edu : <192.168.0.1:32775> : osg-edu.cs.wisc.edu ID OWNER SUBMITTED RUN_TIME HOST(S) 45031.0 roy 4/28 16:27 0+00:00:24 vm1@osgs-c03.cs.wisc.edu
Now let's tell Condor to checkpoint and see what happens. Update this to be appropriate for your job!
% condor_checkpoint <hostname>.cs.wisc.edu
% cat simple.log
000 (45031.000.000) 04/28 16:27:57 Job submitted from host: <192.168.0.1:32775>
...
001 (45031.000.000) 04/28 16:28:07 Job executing on host: <192.168.0.4:33478>
...
006 (45031.000.000) 04/28 16:28:44 Image size of job updated: 10693
...
003 (45031.000.000) 04/28 16:28:44 Job was checkpointed.
Usr 0 00:00:00, Sys 0 00:00:00 - Run Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Run Local Usage
...
005 (45031.000.000) 04/28 16:28:44 Job terminated.
(1) Normal termination (return value 0)
Usr 0 00:00:00, Sys 0 00:00:00 - Run Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Run Local Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Total Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Total Local Usage
715450 - Run Bytes Sent By Job
1142028 - Run Bytes Received By Job
715450 - Total Bytes Sent By Job
1142028 - Total Bytes Received By Job
...
Voila! We checkpointed our job correctly.
Normally, you never need to use condor_checkpoint: we just used it as a demonstration. Condor will checkpoint your jobs periodically (the default is every three hours) or when your job is forced to leave a computer to give time to another user. So you should never need to use condor_checkpoint.
|
|
