From b13a3c3a0196361ba504f0b459398961c2a0f7e6 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zden=C4=9Bk=20=C5=A0ustr?= Date: Wed, 19 Jan 2011 11:09:08 +0000 Subject: [PATCH] First round of changes prior to a new release (new features, versions) --- org.glite.lb.doc/src/LBAG-Running.tex | 10 ++++++++++ org.glite.lb.doc/src/LBUG-Introduction.tex | 4 ++-- org.glite.lb.doc/src/versions.tex | 2 +- 3 files changed, 13 insertions(+), 3 deletions(-) diff --git a/org.glite.lb.doc/src/LBAG-Running.tex b/org.glite.lb.doc/src/LBAG-Running.tex index 5649ef0..07a07d5 100644 --- a/org.glite.lb.doc/src/LBAG-Running.tex +++ b/org.glite.lb.doc/src/LBAG-Running.tex @@ -336,8 +336,18 @@ and tries to upload the files into JP. Details, including the configuration variables, are covered at the following wiki page: + \url{http://egee.cesnet.cz/mediawiki/index.php/LB_purge_and_export_to_JP}. +\paragraph{Persistent Information on Purged Jobs (``Zombies'')} + +Since \LB version 2.0, the JobID of a purged job is not fully discarded but stored in a separate table. A query for the status of such job returns \emph{Identifier removed}.\footnote{As of \LB\,3.0. In 2.0 and 2.1 releases an empty job status structure was returned with job state set to \emph{purged}.} There are two purposes to this arrangement: + +\begin{enumerate} +\item Confirming that the job existed and that its details have been exported to Job Provenance (if deployed and configured), +\item Preventing reuse of the JobID in case of flag \code{EDG\_WLL\_LOGLFLAG\_EXCL} set on registration. +\end{enumerate} + \subsubsection{On-line monitoring and statistics} \label{maintain:statistics} diff --git a/org.glite.lb.doc/src/LBUG-Introduction.tex b/org.glite.lb.doc/src/LBUG-Introduction.tex index b2925fc..6dc2809 100644 --- a/org.glite.lb.doc/src/LBUG-Introduction.tex +++ b/org.glite.lb.doc/src/LBUG-Introduction.tex @@ -754,9 +754,9 @@ because of being (correctly) sorted to an already inactive branch. % purge -- data z~\LB\ zmizí \LB is not a~permanent job data storage. The data get purged from the server on timeout, unrelated to any user's action. -Therefore, the \LB query may return ``no such job'' error message (or not +Therefore, the \LB query may return ``Identifier removed'' error message (or not include the job in a list of retrieved jobs) even if the same previous -\LB query had no such problems. +\LB query behaved differently. \end{itemize} diff --git a/org.glite.lb.doc/src/versions.tex b/org.glite.lb.doc/src/versions.tex index 2c65387..654b303 100644 --- a/org.glite.lb.doc/src/versions.tex +++ b/org.glite.lb.doc/src/versions.tex @@ -45,7 +45,7 @@ The complete \LB Documentation consists of the following parts: \textbf{The following versions of \LB service are covered by these documents:} \begin{itemize} -\item \LBver{2.2}: in development, available through CVS only, +\item \LBver{3.0}: included in the EMI-1 Kebnekaise release \item \LBver{2.1}: replacement for \LBver{2.0} in gLite 3.2, \item \LBver{2.0}: current stable version, in production as part of gLite 3.2, \item \LBver{1.x}: old stable version, in production as part of gLite 3.1. -- 1.8.2.3