[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

4738.0. "maximum thread count reached." by USOPS::HARB () Mon Mar 22 1993 15:33

I tried to setup some historical data recording today
in one domain.

My plan was to record circuit data for phaseIV nodes.
In the domain, I have around 45 nodes, each with about
2-3 active circuits.  So I started the historian process
and proceeded to issue the record requests.

I planned on doing 4:


RECORD NODE4 * LINE * PARTITION=CHARACTERISTICS
RECORD NODE4 * CIRCUIT * PARTITION=STATUS
RECORD NODE4 * CIRCUIT * PARTITION=COUNTERS
REOCRD NODE4 * CIRCUIT * PARTITION=STATISTICS

I figured this would give me everything I needed to go
and look at circuit utilization later.  (That's why I
need the LINE CHARACTERISTICS).

But when I got to the third record, the background
process died with the 'maximum thread count reached'
error message.

How is the maximum thread count set and how can I change
it?  And what do I have to consider when do make that
change?

Thanks,

George
T.RTitleUserPersonal
Name		DateLines
4738.1Is any body out there?USOPS::HARBMon Mar 29 1993 12:438
    Could someone please respond to this note.  I can't keep my historian
    up.  Everytime I start it up a few minutes later, it dies with the same
    error message as noted in .0.
    
    
    Thanks,
    
    George
4738.2TOOK::SHMUYLOVICHMon Mar 29 1993 15:3628
	Sorry for long silence I just came from my vacation.

    This problem is already described in this conference.
    The Historian Background process can handle up to 500 individual
    recording requests ( it means up to 500 different entity/partition pairs).

    The message "maximum thread count reached" indicates that you are trying
    to create 501-st request.

    If you need to record more that 500 entity/partitions you should break
    the recordings into several domains and set up a background process
    for each domain.

    From .0:    
      "In the domain, I have around 45 nodes, each with about
       2-3 active circuits."

    With this numbers you should not create more 500 recording requests.
    Did you specify In Domain qualifier in the Record command? If not
    the wildcard expansion gives you "all known" nodes instead of "all
    nodes from the given domain".

    Also note that you can not record Statistics attribute partition.
    

	Sam
4738.3Is it 1 per request, or per entity/partition?USOPS::HARBWed Mar 31 1993 14:1422
    Thanks for the reply Sam.
    
    The record directive does specify the 'in domain' qualifier.
    
    I did count up the number of entities I am recording on.  I have a
    total of 192 circuits on 45 nodes.  I am using one record command for
    each partition and specifying the wildcard for the entity.  Does that
    count as one request or 192 requests?
    
    Thanks for the note on the 'statistics recording'.  I'll not do that. 
    Which leaves me with just three record requests:
    
    LINE COUNTERS, LINE CHAR, CIRCUIT CHAR.
    
    That makes for either 3 record requests, or 3 * 192 = 576 requests.  If
    it's the first, I should be ok, if it's the second, then I am in
    trouble.  I really don't want to break up this domain.
    
    Any further advise.
    
    
    George
4738.4use CIRCUIT countersCTHQ::WOODCOCKWed Mar 31 1993 16:1911
>>    LINE COUNTERS, LINE CHAR, CIRCUIT CHAR.


George,

I'm not sure if the above records will work for getting stats. We always use
*CIRCUIT* counters, LINE CHAR, CIRCUIT CHAR. LINE counters might work but if
not switch to circuit counters.

best regards,
brad...