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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

784.0. "Mail Queue was busy" by MSDSWS::DUNCAN (I'm in trouble again!) Tue Jun 02 1992 16:48

    V2.4
    
    I've seen the note in the _v24 conference and I've seen the Stars
    (article) but I can't seem to see the light!!! ;-)
    
    We are getting the following error quite a bit:
    
     1-JUN-1992 09:08:42           %OA-E-PENDING_QUEUE_B, Mail queue was
    busy - delivery incomplete
     1-JUN-1992 09:08:43           %OA-E-PENDING_QUEUE_B, Mail queue was
    busy - delivery incomplete
    
    And FWIW:
    
     1-JUN-1992 09:24:26           %OA-E-RECORD_IO_ERROR, Error occurred
    while attempting to GET the record
     1-JUN-1992 09:24:27           -RMS-E-RLK, target record currently
    locked by another stream
     1-JUN-1992 10:19:29           %OA-E-RECORD_IO_ERROR, Error occurred
    while attempting to GET the record
     1-JUN-1992 10:19:29           -RMS-E-RLK, target record currently
    locked by another stream
    
    
    The Customer is running ALL-IN-1 in a cluster with the users only
    accessing it on a 9000 while the sender and fetcher can run on another
    9000 or 2 8820's.  The 9000 with the ALL-IN-1 users is loaded at 90 -
    100% cpu usage.  
    
    I find it hard to believe that the pending file could stay locked for
    over 30 seconds on a 9000, even it it is loaded! (I think that is what
    the stars article said??)
    
    Any help is greatly needed!
    
    
    Thanks in advance,
    Darryl
T.RTitleUserPersonal
Name		DateLines
784.1Disk speed is the limiting factorAIMTEC::PORTER_TTerry Porter, ALL-IN-1 Support, Atlanta CSCTue Jun 02 1992 18:4716
I have only ever seen this message when accessing the PENDING queue (typically
the sender queue but could happen to any queue in theory) and the I/O times
out (as you say the timeout is at 30 seconds).

Typically the cause is not CPU usage but an overloaded disk. Monitor the disk
that has the PENDING file on it and look at the average queue size. (MONITOR 
DISK/ITEM=QUEUE) If there is any significant average queue then the disk is
overloaded. A reasonably loaded disk should have a average queue well below
0.1 an average queue of 1, 2 or more indicates a heavily overloaded disk.

If this is the problem look at the files on that disk and see what can be moved
to a more lightly loaded disk.

HTH

Terry