/usr/share/doc/condor/html/3_1_Introduction.html is in condor-doc 7.8.2~dfsg.1-1+deb7u3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--Converted with LaTeX2HTML 2008 (1.71)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>3.1 Introduction</TITLE>
<META NAME="description" CONTENT="3.1 Introduction">
<META NAME="keywords" CONTENT="ref">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2008">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="ref.css">
<LINK REL="next" HREF="3_2_Installation.html">
<LINK REL="previous" HREF="3_Administrators_Manual.html">
<LINK REL="up" HREF="3_Administrators_Manual.html">
<LINK REL="next" HREF="3_2_Installation.html">
</HEAD>
<BODY BGCOLOR=#FFFFFF >
<DIV CLASS="navigation"><!--Navigation Panel-->
<A NAME="tex2html1295"
HREF="3_2_Installation.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1289"
HREF="3_Administrators_Manual.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1283"
HREF="3_Administrators_Manual.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1291"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1293"
HREF="Index.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1296"
HREF="3_2_Installation.html">3.2 Installation</A>
<B> Up:</B> <A NAME="tex2html1290"
HREF="3_Administrators_Manual.html">3. Administrators' Manual</A>
<B> Previous:</B> <A NAME="tex2html1284"
HREF="3_Administrators_Manual.html">3. Administrators' Manual</A>
<B> <A NAME="tex2html1292"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html1294"
HREF="Index.html">Index</A></B>
<BR>
<BR></DIV>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL CLASS="ChildLinks">
<LI><A NAME="tex2html1297"
HREF="3_1_Introduction.html#SECTION00411000000000000000"><SPAN CLASS="arabic">3</SPAN>.<SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">1</SPAN> The Different Roles a Machine Can Play</A>
<LI><A NAME="tex2html1298"
HREF="3_1_Introduction.html#SECTION00412000000000000000"><SPAN CLASS="arabic">3</SPAN>.<SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">2</SPAN> The Condor Daemons</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION00410000000000000000"></A><A NAME="sec:Admin-Intro"></A>
<BR>
<SPAN CLASS="arabic">3</SPAN>.<SPAN CLASS="arabic">1</SPAN> Introduction
</H1>
<P>
This is the Condor Administrator's Manual for Unix.
Its purpose is to aid in
the installation and administration of a Condor pool. For help on
using Condor, see the Condor User's Manual.
<P>
A Condor pool
<A NAME="8489"></A>
<A NAME="8490"></A>
is comprised of a single machine which serves as the
<SPAN CLASS="textit">central manager</SPAN>,
<A NAME="8492"></A>
and an arbitrary number of other machines that
have joined the pool. Conceptually, the pool is a collection of
resources (machines) and resource requests (jobs). The role of Condor
is to match waiting requests with available resources. Every part of
Condor sends periodic updates to the central manager, the centralized
repository of information about the state of the pool. Periodically,
the central manager assesses the current state of the pool and tries
to match pending requests with the appropriate resources.
<P>
Each resource has an owner,
<A NAME="8493"></A>
<A NAME="8494"></A>
the user who works at the machine. This
person has absolute power over their own resource and Condor goes out
of its way to minimize the impact on this owner caused by Condor. It
is up to the resource owner to define a policy for when Condor
requests will
serviced and when they will be denied.
<P>
Each resource request has an owner as well: the
user who submitted the job. These people want Condor to provide as
many CPU cycles as possible for their work. Often the interests of
the resource owners are in conflict with the interests of the resource
requesters.
<P>
The job of the Condor administrator is to configure the Condor pool to
find the happy medium that keeps both resource owners and users of
resources satisfied. The purpose of this manual is to help you
understand the mechanisms that Condor provides to enable you to find
this happy medium for your particular set of users and resource owners.
<P>
<H2><A NAME="SECTION00411000000000000000"></A><A NAME="sec:Machine-Roles"></A>
<BR>
<SPAN CLASS="arabic">3</SPAN>.<SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">1</SPAN> The Different Roles a Machine Can Play
</H2>
<P>
Every machine in a Condor pool can serve a variety of roles. Most
machines serve more than one role simultaneously. Certain roles can
only be performed by single machines in your pool. The following list
describes what these roles are and what resources are required on the
machine that is providing that service:
<P>
<DL>
<DD><P>
<A NAME="8497"></A>
<A NAME="8498"></A>
</DD>
<DT><STRONG>Central Manager</STRONG></DT>
<DD>There can be only one central manager for your
pool. The machine is the collector of information, and the negotiator
between resources and resource requests. These two halves of the
central manager's responsibility are performed by separate daemons, so
it would be possible to have different machines providing those two
services. However, normally they both live on the same machine. This
machine plays a very important part in the Condor pool and should be
reliable. If this machine crashes, no further matchmaking can be
performed within the Condor system (although all current matches
remain in effect until they are broken by either party involved in the
match). Therefore, choose for central manager
a machine that is likely to be
up and running all the time, or at least one that will be rebooted quickly if
something goes wrong.
The central manager will
ideally have a good network connection to all the
machines in your pool, since they all send updates over the network to
the central manager. All queries go to the central manager.
<P>
<A NAME="8499"></A>
<A NAME="8500"></A>
</DD>
<DT><STRONG>Execute</STRONG></DT>
<DD>Any machine in your pool (including your Central
Manager) can be configured for whether or not it should execute Condor
jobs. Obviously, some of your machines will have to serve this
function or your pool won't be very useful. Being an execute machine
doesn't require many resources at all. About the only resource that
might matter is disk space, since if the remote job dumps core, that
file is first dumped to the local disk of the execute machine before
being sent back to the submit machine for the owner of the job.
However, if there isn't much disk space, Condor will simply limit the
size of the core file that a remote job will drop. In general the
more resources a machine has (swap space, real memory, CPU speed,
etc.) the larger the resource requests it can serve. However, if
there are requests that don't require many resources, any machine
in your pool could serve them.
<P>
<A NAME="8501"></A>
<A NAME="8502"></A>
</DD>
<DT><STRONG>Submit</STRONG></DT>
<DD>Any machine in your pool (including your Central
Manager) can be configured for whether or not it should allow Condor
jobs to be submitted.
The resource requirements for a submit machine
are actually much greater than the resource requirements for an
execute machine. First of all, every job that you submit that is
currently running on a remote machine generates another process on
your submit machine. So, if you have lots of jobs running, you will
need a fair amount of swap space and/or real memory. In addition all
the checkpoint files from your jobs are stored on the local disk of
the machine you submit from. Therefore, if your jobs have a large
memory image and you submit a lot of them, you will need a lot of disk
space to hold these files. This disk space requirement can be
somewhat alleviated with a checkpoint server (described below),
however the binaries of the jobs you submit are still stored on the
submit machine.
<P>
<A NAME="8503"></A>
<A NAME="8504"></A>
</DD>
<DT><STRONG>Checkpoint Server</STRONG></DT>
<DD>One machine in your pool can be configured as
a checkpoint server.
This is optional, and is not part of the
standard Condor binary distribution. The checkpoint server is a
centralized machine that stores all the checkpoint files for the jobs
submitted in your pool. This machine should have lots of disk space
and a good network connection to the rest of your pool, as the traffic
can be quite heavy.
<P>
</DD>
</DL>
<P>
Now that you know the various roles a machine can play in a Condor
pool, we will describe the actual daemons within Condor that implement
these functions.
<P>
<H2><A NAME="SECTION00412000000000000000"></A><A NAME="sec:Condor-Daemons"></A>
<A NAME="8507"></A>
<A NAME="8508"></A>
<BR>
<SPAN CLASS="arabic">3</SPAN>.<SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">2</SPAN> The Condor Daemons
</H2>
<P>
The following list describes all the daemons and programs that could
be started under Condor and what they do:
<P>
<DL>
<DD><P>
<A NAME="8635"></A>
<A NAME="8636"></A>
<A NAME="8512"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_master</SPAN></STRONG></DT>
<DD>This daemon
is responsible for keeping all the
rest of the Condor daemons running on each machine in your pool. It
spawns the other daemons, and periodically checks to see if there are
new binaries installed for any of them. If there are, the master will
restart the affected daemons. In addition, if any daemon crashes, the
master will send e-mail to the Condor Administrator of your pool and
restart the daemon. The <SPAN CLASS="textit">condor_master</SPAN> also supports various
administrative commands that let you start, stop or reconfigure
daemons remotely. The <SPAN CLASS="textit">condor_master</SPAN> will run on every machine in
your Condor pool, regardless of what functions each machine are
performing.
<P>
<A NAME="8637"></A>
<A NAME="8638"></A>
<A NAME="8518"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_startd</SPAN></STRONG></DT>
<DD>This daemon
represents a given resource
(namely, a machine capable of running jobs) to the Condor pool. It
advertises certain attributes about that resource that are used to
match it with pending resource requests. The startd will run on any
machine in your pool that you wish to be able to execute jobs. It is
responsible for enforcing the policy that resource owners configure
which determines under what conditions remote jobs will be started,
suspended, resumed, vacated, or killed. When the startd is ready to
execute a Condor job, it spawns the <SPAN CLASS="textit">condor_starter</SPAN>, described below.
<P>
<A NAME="8639"></A>
<A NAME="8640"></A>
<A NAME="8523"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_starter</SPAN></STRONG></DT>
<DD>This program
is the entity that actually
spawns the remote Condor job on a given machine. It sets up the
execution environment and monitors the job once it is running. When a
job completes, the starter notices this, sends back any status
information to the submitting machine, and exits.
<P>
<A NAME="8641"></A>
<A NAME="8642"></A>
<A NAME="8527"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_schedd</SPAN></STRONG></DT>
<DD>This daemon
represents resource requests to
the Condor pool. Any machine that you wish to allow users to submit
jobs from needs to have a <SPAN CLASS="textit">condor_schedd</SPAN> running. When users submit
jobs, they go to the schedd, where they are stored in the <SPAN CLASS="textit">job
queue</SPAN>, which the schedd manages. Various tools to view and
manipulate the job queue (such as <SPAN CLASS="textit">condor_submit</SPAN>, <SPAN CLASS="textit">condor_q</SPAN>, or
<SPAN CLASS="textit">condor_rm</SPAN>) all must connect to the schedd to do their work. If the
schedd is down on a given machine, none of these commands will work.
<P>
The <SPAN CLASS="textit">condor_schedd</SPAN> advertises the number of waiting jobs in its job queue and
is responsible for claiming available resources to serve those
requests. Once a schedd has been matched with a given resource, the
schedd spawns a <SPAN CLASS="textit">condor_shadow</SPAN> (described below) to serve that
particular request.
<P>
<A NAME="8643"></A>
<A NAME="8644"></A>
<A NAME="8538"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_shadow</SPAN></STRONG></DT>
<DD>This program
runs on the machine where a given
request was submitted and acts as the resource manager for the
request. Jobs that are linked for Condor's standard universe, which
perform remote system calls, do so via the <SPAN CLASS="textit">condor_shadow</SPAN>. Any
system call performed on the remote execute machine is sent over the
network, back to the <SPAN CLASS="textit">condor_shadow</SPAN> which actually performs the
system call (such as file I/O) on the submit machine, and the result
is sent back over the network to the remote job. In addition, the
shadow is responsible for making decisions about the request (such as
where checkpoint files should be stored, how certain files should be
accessed, etc).
<P>
<A NAME="8645"></A>
<A NAME="8646"></A>
<A NAME="8544"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_collector</SPAN></STRONG></DT>
<DD>This daemon
is responsible for collecting
all the information about the status of a Condor pool. All other
daemons periodically send ClassAd updates to
the collector. These ClassAds contain all the information about the
state of the daemons, the resources they represent or resource
requests in the pool (such as jobs that have been submitted to a given
schedd). The <SPAN CLASS="textit">condor_status</SPAN> command can be used to query the
collector for specific information about various parts of Condor. In
addition, the Condor daemons themselves query the collector for
important information, such as what address to use for sending
commands to a remote machine.
<P>
<A NAME="8647"></A>
<A NAME="8648"></A>
<A NAME="8549"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_negotiator</SPAN></STRONG></DT>
<DD>This daemon
is responsible for all the
match-making within the Condor system. Periodically, the negotiator
begins a <SPAN CLASS="textit">negotiation cycle</SPAN>, where it queries the collector for
the current state of all the resources in the pool. It contacts each
schedd that has waiting resource requests in priority order, and tries
to match available resources with those requests. The negotiator is
responsible for enforcing user priorities in the system, where the
more resources a given user has claimed, the less priority they have
to acquire more resources. If a user with a better priority has jobs
that are waiting to run, and resources are claimed by a user with a
worse priority, the negotiator can preempt that resource and match it
with the user with better priority.
<P>
<SPAN ID="txt8747">NOTE</SPAN>: A higher numerical value of the user priority in Condor
translate into worse priority for that user. The best priority you
can have is 0.5, the lowest numerical value, and your priority gets
worse as this number grows.
<P>
<A NAME="8649"></A>
<A NAME="8650"></A>
<A NAME="8554"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_kbdd</SPAN></STRONG></DT>
<DD>This daemon
is used on Linux and Windows.
On those platforms, the <SPAN CLASS="textit">condor_startd</SPAN> frequently cannot determine
console (keyboard or mouse) activity directly from the system, and
requires a separate process to do so.
On Linux, the
<SPAN CLASS="textit">condor_kbdd</SPAN> connects to the X Server and periodically checks to see
if there has been any activity.
On Windows, the <SPAN CLASS="textit">condor_kbdd</SPAN> runs as the logged-in user and registers
with the system to receive keyboard and mouse events.
When it detects console activity, the <SPAN CLASS="textit">condor_kbdd</SPAN> sends a
command to the startd. That way, the startd knows the machine owner
is using the machine again and can perform whatever actions are
necessary, given the policy it has been configured to enforce.
<P>
<A NAME="8651"></A>
<A NAME="8652"></A>
<A NAME="8562"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_ckpt_server</SPAN></STRONG></DT>
<DD>This is the checkpoint server.
It services requests to store and retrieve checkpoint files. If your
pool is configured to use a checkpoint server but that machine (or the
server itself is down) Condor will revert to sending the checkpoint
files for a given job back to the submit machine.
<P>
<A NAME="8653"></A>
<A NAME="8654"></A>
<A NAME="8566"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_gridmanager</SPAN></STRONG></DT>
<DD>This daemon
handles management and execution of all <SPAN CLASS="textbf">grid</SPAN>
universe jobs.
The <SPAN CLASS="textit">condor_schedd</SPAN> invokes the <SPAN CLASS="textit">condor_gridmanager</SPAN> when
there are <SPAN CLASS="textbf">grid</SPAN> universe jobs in the queue,
and the <SPAN CLASS="textit">condor_gridmanager</SPAN> exits when there are no more
<SPAN CLASS="textbf">grid</SPAN> universe jobs in the queue.
<P>
<A NAME="8655"></A>
<A NAME="8656"></A>
<A NAME="8576"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_credd</SPAN></STRONG></DT>
<DD>This daemon
runs on Windows platforms to manage password storage in a secure manner.
<P>
<A NAME="8657"></A>
<A NAME="8658"></A>
<A NAME="8580"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_had</SPAN></STRONG></DT>
<DD>This daemon
implements the high availability of a pool's central manager
through monitoring the communication of necessary daemons.
If the current, functioning, central manager machine
stops working, then this daemon ensures that another
machine takes its place, and becomes the central manager of
the pool.
<P>
<A NAME="8659"></A>
<A NAME="8660"></A>
<A NAME="8584"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_replication</SPAN></STRONG></DT>
<DD>This daemon
assists the <SPAN CLASS="textit">condor_had</SPAN> daemon by keeping an updated copy of the
pool's state. This state provides a better transition
from one machine to the next, in the event
that the central manager machine stops working.
<P>
<A NAME="8661"></A>
<A NAME="8662"></A>
<A NAME="8589"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_transferer</SPAN></STRONG></DT>
<DD>This short lived daemon is invoked by
the <SPAN CLASS="textit">condor_replication</SPAN> daemon to accomplish the task of transferring
a state file before exiting.
<P>
<A NAME="8663"></A>
<A NAME="8664"></A>
<A NAME="8594"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_procd</SPAN></STRONG></DT>
<DD>This daemon
controls and monitors process families within Condor. Its use
is optional in general but it must be used if privilege separation
(see Section <A HREF="3_6_Security.html#sec:PrivSep">3.6.14</A>) or group-ID based tracking (see
Section <A HREF="3_12_Setting_Up.html#sec:GroupTracking">3.12.11</A>) is enabled.
<P>
<A NAME="8665"></A>
<A NAME="8666"></A>
<A NAME="8600"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_job_router</SPAN></STRONG></DT>
<DD>This daemon
transforms <SPAN CLASS="textbf">vanilla</SPAN> universe jobs into <SPAN CLASS="textbf">grid</SPAN>
universe jobs, such that the transformed jobs are capable
of running elsewhere, as appropriate.
<P>
<A NAME="8667"></A>
<A NAME="8668"></A>
<A NAME="8606"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_lease_manager</SPAN></STRONG></DT>
<DD>This daemon
manages leases in a persistent manner.
Leases are represented by ClassAds.
<P>
<A NAME="8669"></A>
<A NAME="8670"></A>
<A NAME="8610"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_rooster</SPAN></STRONG></DT>
<DD>This daemon wakes hibernating machines based
upon configuration details.
<P>
<A NAME="8671"></A>
<A NAME="8672"></A>
<A NAME="8614"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_defrag</SPAN></STRONG></DT>
<DD>This daemon manages draining of machines
with fragmented partitionable slots so that they become available
for jobs requiring a whole machine or larger fraction of a machine.
<P>
<A NAME="8673"></A>
<A NAME="8674"></A>
<A NAME="8618"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_shared_port</SPAN></STRONG></DT>
<DD>This daemon listens for incoming TCP packets
on behalf of Condor daemons, thereby reducing the number of required
ports that must be opened when Condor is accessible through a firewall.
<P>
</DD>
</DL>
<P>
When compiled from source code,
the following daemons may be compiled in to provide optional functionality.
<DL>
<DD><P>
<A NAME="8675"></A>
<A NAME="8676"></A>
<A NAME="8624"></A>
</DD>
<DT><STRONG><SPAN CLASS="textit">condor_hdfs</SPAN></STRONG></DT>
<DD>This daemon manages the configuration of a
Hadoop file system as well as the invocation of a properly configured
Hadoop file system.
<P>
</DD>
</DL>
<P>
See figure <A HREF="#fig:pool-arch">3.1</A> for a graphical representation of the
pool architecture.
<P>
<DIV ALIGN="CENTER"><A NAME="fig:pool-arch"></A><A NAME="8677"></A>
<TABLE>
<CAPTION ALIGN="BOTTOM"><STRONG>Figure 3.1:</STRONG>
Pool Architecture</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
</DIV><IMG
WIDTH="464" HEIGHT="357" ALIGN="BOTTOM" BORDER="0"
SRC="img11.png"
ALT="\includegraphics{admin-man/pool-arch.eps}"></TD></TR>
</TABLE>
</DIV>
<DIV CLASS="navigation"><HR>
<!--Navigation Panel-->
<A NAME="tex2html1295"
HREF="3_2_Installation.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1289"
HREF="3_Administrators_Manual.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1283"
HREF="3_Administrators_Manual.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1291"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1293"
HREF="Index.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1296"
HREF="3_2_Installation.html">3.2 Installation</A>
<B> Up:</B> <A NAME="tex2html1290"
HREF="3_Administrators_Manual.html">3. Administrators' Manual</A>
<B> Previous:</B> <A NAME="tex2html1284"
HREF="3_Administrators_Manual.html">3. Administrators' Manual</A>
<B> <A NAME="tex2html1292"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html1294"
HREF="Index.html">Index</A></B> </DIV>
<!--End of Navigation Panel-->
<ADDRESS>
condor-admin@cs.wisc.edu
</ADDRESS>
</BODY>
</HTML>
|