Changes between Version 13 and Version 14 of shepherding_the_pstamp_server

Timestamp:

Feb 16, 2016, 10:56:58 AM (10 years ago)

Author:

bills

Comment:

--

shepherding_the_pstamp_server

@@ -137 +137 @@
 }}}
 
-'''Note: Much of the next few paragraphs no longer applies due to the aboliton of magic.'''
 
 pstamp_checkdependent.pl sets chipRun 77563, class_id XY31 to update state and watches for it to
-go to 'full' state. Once it' goes to full it sets the magicDSRun to 'new' state. Once the component
-is destreaked chipProcessedImfile.magicked > 0 it's done and the pstampDependent is set to 'full'
-
-The update processing is managed by the 'update' pantasks.
+go to 'full' state.  Once that happens  the state of the pstampDependent is set to 'full'
+
+The update processing is managed by the 'stdscience' pantasks except for the ps_ud_QUB label which
+is being run somewhere else.
 
 When a dependent run faults (that is when a
@@ -171 +170 @@
 }}}
 
-To make a request and it's jobs just go away set the request's state to goto_cleaned. -- what is the command example to do so??
+If just a few jobs are affected by the outage, then the rest of the request can 
+
+To make a request and it's jobs just go away set the request's state to goto_cleaned with the command
+
+{{{
+pstamptool -dbname ippRequestServer -dbserver $PSDBSERVER -updatereq  -set_state goto_cleaned -req_id 182918
+}}}
+
  * could the fault also be set to an error code if known what the fault is -- like 25 for data(old) that isn't updating properly?
 
-pst -updatereq -set_state goto_cleaned -req_id NNNNNNN
 
 
@@ -217 +222 @@
 the data store.
 
-