Operating System - OpenVMS
1820048 Members
3283 Online
109608 Solutions
New Discussion юеВ

Adjusting CLUSTER_CREDITS

 
SOLVED
Go to solution
Jack Trachtman
Super Advisor

Adjusting CLUSTER_CREDITS

2-node cluster
VMS V7.3-2

I have noticed (via SHOW CLUSTER/CONTINUOUS) that there are occassional Cluster Waits occurring. I am planning to adjust the CLUSTER_CREDITS setting to reduce/eliminate these waits.

The present CLUSTER_CREDITS setting on both nodes is 30 and the max is (I think) 128. One HP doc recommends changing the setting in increments of 5.

Since this is a static parameter and I can't get these systems down very often, I was wondering how others decide on selecting a CLUSTER_CREDITS value.

TIA
2 REPLIES 2
Andy Bustamante
Honored Contributor

Re: Adjusting CLUSTER_CREDITS


You may also want to consider checking your network (assuming a ethernet cluster interconnect). Use

$ MCR LANCP SHOW DEV /COUNT

The bandwidth on the network may also be a factor. A second interface with a cross over cable makes a very reliable second interface. Other than confirming the speed/duplex there is no other configuration required.


Andy
If you don't have time to do it right, when will you have time to do it over? Reach me at first_name + "." + last_name at sysmanager net
John Gillings
Honored Contributor
Solution

Re: Adjusting CLUSTER_CREDITS

Jack,

Always keep in mind that most SYSGEN defaults were formulated quite some time ago, when resource costs were considerably higher than they are today.

Each buffer is SCSMAXMSG bytes in size (or maybe the default buffer size of the interconnect device?). You have CLUSTER_CREDITS * MAX(SCSMAXMSG,device buffer size) * Number-of-other-cluster-nodes bytes allocated in non-paged-pool. In your case it's only one other node, so the overhead probably isn't too significant, and you probably have orders of magnitude more memory than was expected when the default value was chosen.

Since you don't have much system downtime, if you're concerned about potential NPAGEDYN issues, start with (say) 60 and keep an eye on NPAGEDYN consumption.

If you've got a decent amount of memory, don't spend too much time worrying about it, just crank CLUSTER_CREDITS up to maximum (128), and add the line to MODPARAMS:

ADD_NPAGEDYN=CLUSTER_CREDITS*SCSMAXMSG

Also note that you only need to increase the node that's experiencing credit waits. There is no need for the parameters to be equal on both nodes.
A crucible of informative mistakes