[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5259.0. "Poll failure" by GLDOA::KATZ (Follow your conscience) Thu Jun 24 1993 13:41

    We run our export procedures from a batch queue.
    Many times the polling fails
    
               Time of last failed poll = "23-JUN-1993 21:49:46.71",
               Last poll failure reason = "schedule time passed",
    
    Does this indicate that the batch job never got run for time it was
    submitted? We of course purge our logs so there is not a record
    of the failure. I believe that our system, a VAX 3100 with 32MB
    of memory is overloaded and could be causing these failures.
    Any ideas?  Thanks.
    
    		-Jim-
T.RTitleUserPersonal
Name
DateLines
5259.1A VS3100 is too smallTOOK::R_SPENCENets don't fail me now...Thu Jun 24 1993 16:2611
    A VAXstation (it IS a VAXstation?) 3100 of any sort is not supported
    by any current version of DECmcc. 32 mb is a it on the light size (one
    reasone we can't support VS3100s) and the SPD lists 48mb as a minimum.
    
    Keep in mind that a minimum config will work correctly doing a minimum
    number of things.
    
    I suspect that your configuration is slow enough that things are taking
    too long and scheduled times are being missed.
    
    s/rob
5259.2Try delay argument for background processTOOK::SHMUYLOVICHThu Jun 24 1993 16:4518
>>		 I believe that our system, a VAX 3100 with 32MB
>>    of memory is overloaded and could be causing these failures.

    You are right, your system is overloaded.

    You can try to decrease the pick load from the exporter by using the 
    second argument to the background process. This argument introduces
    a delay (in seconds) between exporting requests execution It prevents
    exporting requests from competing for execution. Please, remember that
    this will delay the first execution of all requests except the first one.
    For example, if you have 10 active exportings and specify delay as
    60 (1 minute) the last exporting will be "activated" in 10 minutes after
    the background restarts.

	Sam