Author: challngr
Date: Thu Oct 10 13:57:49 2013
New Revision: 1530980
URL: http://svn.apache.org/r1530980
Log:
UIMA-2682 Remove references to Implicit and Submitted services.
Modified:
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part1/terminology.tex
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/services.tex
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/webserver/services.tex
Modified:
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part1/terminology.tex
URL:
http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part1/terminology.tex?rev=1530980&r1=1530979&r2=1530980&view=diff
==============================================================================
---
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part1/terminology.tex
(original)
+++
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part1/terminology.tex
Thu Oct 10 13:57:49 2013
@@ -15,11 +15,6 @@
\item[DUCC] Distributed UIMA Cluster Computing.
-\item[Implicit service] An implicit service is a service that is started
externally to DUCC but
- referenced by some dependent service or job. DUCC will attempt to contact
the service using
- the dependency string. If contact is successful the job is started,
otherwise it is
- terminated before resources are allocated to it.
-
\item[Registered service] A registered service is a service that is registered
with DUCC. DUCC
saves the service specification and fully manages the service, insuring it
is running when needed,
and shutdown when not.
Modified:
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex
URL:
http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex?rev=1530980&r1=1530979&r2=1530980&view=diff
==============================================================================
---
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex
(original)
+++
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex
Thu Oct 10 13:57:49 2013
@@ -445,12 +445,7 @@ ducc_services --modify UIMA-AS:Service23
If no id is given, information about all services is returned.
- Below is a query against a system with three services.
-
- The service with endpoint {\tt
UIMA-AS:FixedSleepAE\_6:tcp://bobmach291:61617} is a service
- submitted outside of DUCC so it is marked as Implicit and has no
implementing processes that
- are known to DUCC. It is used by job 0 (``References'') and is active,
available, and being
- actively pinged. The ActiveMq queue statistics are shown.
+ Below is a sample service query.
The service with endpoint {\tt
UIMA-AS:FixedSleepAE\_5:tcp://bobmach:61617} is a
registered service, whose registered numeric id is 2. It is registered
for two instances and
@@ -460,24 +455,8 @@ ducc_services --modify UIMA-AS:Service23
instances whose DUCC Ids are 9 and 5. It is currently used (referenced)
by DUCC jobs 1 and 5.
- The service with endpoint {\tt
UIMA-AS:FixedSleepAE\_1:tcp://bobmach:61617} is a
- submitted service. It was submitted twice, and so has two implementers,
DUCC service
- jobs 0 and 1. It is referenced by job 7. It will continue to run until
somebody cancels it,
- even if it is not used.
\begin{verbatim}
-Service: UIMA-AS:FixedSleepAE_6:tcp://bobmach291:61617
-Service Class : Implicit
-Implementors : (N/A)
-References : 0
-Dependencies : none
-Service State : Available
-Ping Active : true
-Autostart : false
-Manual Stop : false
-Queue Statistics:
-Consum Prod Qsize minNQ maxNQ expCnt inFlgt DQ NQ Disp
- 78 240 170 2 36414 0 0 636 806 636
Service: UIMA-AS:FixedSleepAE_5:tcp://bobmach291:61617
Service Class : Registered as ID 2 instances[2] linger[5]
@@ -491,19 +470,6 @@ Manual Stop : false
Queue Statistics:
Consum Prod Qsize minNQ maxNQ expCnt inFlgt DQ NQ Disp
52 44 0 0 3 0 0 402 402 402
-
-Service: UIMA-AS:FixedSleepAE_1:tcp://bobmach291:61617
-Service Class : Submitted
-Implementors : 1 0
-References : 7
-Dependencies : none
-Service State : Available
-Ping Active : true
-Autostart : false
-Manual Stop : false
-Queue Statistics:
-Consum Prod Qsize minNQ maxNQ expCnt inFlgt DQ NQ Disp
- 52 0 0 1 1504371 0 0 35 35 35
\end{verbatim}
\end{description}
\paragraph{Notes:}
Modified:
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/services.tex
URL:
http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/services.tex?rev=1530980&r1=1530979&r2=1530980&view=diff
==============================================================================
---
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/services.tex
(original)
+++
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/services.tex
Thu Oct 10 13:57:49 2013
@@ -74,68 +74,22 @@
service endpoints int their specifications. See the
\hyperref[sec:cli.ducc-submit]{\em job } and
\hyperref[sec:cli.ducc-services]{\em services } CLI descriptions for
details.
-
-
- \section{Service Classes.}
- \label{sec:service.classes}
- Services may be started externally to DUCC, or as registered services.
It is
- possible to register a ``ping-only'' CUSTOM service that has no process
managed by DUCC,
- consisting only of a pinger. To distinguish among the various
behaviours and management
- mechanisms for service we define a number of {\em service classes}.
-
- \subsection{Implicit Services.}
- \label{sec:services.implicit}
- An implicit service is started externally to DUCC and discovered by DUCC
only when it is
- referenced by a job's {\em service\_dependency} parameter. Such a
service is called
- an {\em implicit} service.
-
- If the service dependency is a UIMA-AS service, or if it is a registered
CUSTOM service,
- the SM sets up a "ping" thread based on the
- service endpoint of the dependency to discover if the service exists at
the endpoint. If so,
- the SM updates its list of known services and marks the job "ready to
schedule". If neither
- of these cases is true the job is ``refused'' by the Service Manager,
causing DUCC to cancel
- the job.
-
- When jobs referencing implicit services exit, a timer is set and DUCC
continues to monitor the
- service against the possibility that subsequent jobs will need it. Once
the last job using the
- service has exited and the service timer expired, the SM stops the
monitors and purges the
- service from its records.
-
- \subsubsection{Implicit UIMA-AS services}
- If a job \hyperref[sec:service.endpoints]{references} a UIMA-AS service
that is not known to the
- DUCC Service Manager, the Service Manager will start
- its default internal pinger. The default pinger uses JMX to monitor the
ActiveMQ queue statistics,
- and also issues UIMA-AS ``get-meta'' requests to the service to insure
it is responsive. The
- service is monitored throughout the lifetime of the job.
-
- If the service should stop
- responding, its state is updated to "not-responding" but the job is
allowed to continue as
- DUCC cannot tell if the job is using the service. New jobs are not
granted resources if
- their pre-requisite services are not active, as determined by the ping
process.
-
- \subsubsection{Implicit CUSTOM services, or ``ping-only'' Service}
- If a job \hyperref[sec:service.endpoints]{references} a CUSTOM service,
the service must be
- registered and have a CUSTOM \hyperref[sec:service.pingers]{pinger}
associated with it. Such a
- service is referred to as a ``ping-only'' service. DUCC will start the
pinger and monitor the
- service as expected.
-
- A CUSTOM pinger is written to an interface defined by the DUCC API. The
pinger may perform
- any action needed to determine if the CUSTOM service is active and
responsive and may return
- a string for display in the web server, summarizing service statistics.
+
+ All services must be registered with DUCC. It is
+ possible to register a ``ping-only'' service that has no process managed
by DUCC,
+ consisting only of a pinger.
- \subsection{Registered Services.}
\hyperref[sec:cli.ducc-services]{Registered services} are
- fully managed by DUCC. A service is registered with DUCC using the
+ A service is registered with DUCC using the
\hyperref[sec:cli.ducc-services]{ducc\_services} CLI. Service
registrations are persisted by
DUCC and last over DUCC and cluster restarts.
- Note that if an incoming job references a service that is not registered
and which is not
- responsive to the default pinger, that job is marked ``Services
Unavailable'' and canceled
- by the system.
+ An incoming job which references a service that is not registered is
marked ``Services
+ Unavailable'' and canceled by the system.
- There are several variants on Registered Services:
+ There are several variants on services:
\begin{description}
- \item[Autostarted Services] An autostarted service is a registered
service that is
+ \item[Autostarted Services] An autostarted service is a service that
is
automatically started when the DUCC system is started. When DUCC is
started, the SM checks the
service registry for all service that are marked for automatic
start-up. If registered for autostart,
the DUCC Service Manager submits the registered number of instances
@@ -158,7 +112,7 @@
\item[Ping-Only Services]
\phantomsection\label{subsub:services.ping-only}
- \hyperref[sec:services.implicit]{Ping-only services} consist of only
+ Ping-only services consist of only
a ping thread. The service itself is not managed in any way by
DUCC. This is useful for
managing dependencies on services that are not under DUCC control:
DUCC can detect and
report on the health of these services and take appropriate actions
on dependent jobs if
@@ -400,7 +354,7 @@ public class CustomPing
\end{verbatim}
where $<$serviceid$>$ is the id returned when you registered the pinger.
- \paragraph{4. f all else fails ...}
+ \paragraph{4. If f all else fails ...}
If your pinger does not work and you cannot determine the reason, be sure
you enable {\em service\_ping\_dolog} and
look in your log directory, as most problems with pingers are reflected
there. As a last resort, you can
inspect the the Service Manager's log in
Modified:
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/webserver/services.tex
URL:
http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/webserver/services.tex?rev=1530980&r1=1530979&r2=1530980&view=diff
==============================================================================
---
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/webserver/services.tex
(original)
+++
uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/webserver/services.tex
Thu Oct 10 13:57:49 2013
@@ -16,15 +16,10 @@
This is the unique service endpoint of the service.
\item[Type] \hfill \\
- This is the service type.
-
- There are a number of variants on service types, as discussed in
the
- \hyperref[sec:services.types]{services} section of this book.
The web server
- simplifies these into the following three values:
+ This is the service type, which is one of
\begin{itemize}
\item Registered
- \item Submitted
- \item Implicit
+ \item Ping-Only
\end{itemize}
\item[State] \hfill \\
