topic NODE_TIMEOUT value? in Operating System - HP-UX

NODE_TIMEOUT value?

dictum9 — Wed, 16 Aug 2006 14:02:55 GMT

The NODE_TIMEOUT value is set to 6,000,000 in the /etc/cmcluster/ directory.

Does this mean it's set to 6 seconds?

I need it set to 8 seconds, how do I change it, and what needs to be done for the change to take effect after modifying the file?

Re: NODE_TIMEOUT value?

Pupil_1 — Wed, 16 Aug 2006 14:11:56 GMT

8 sec means 8000000 micro seconds.

Re: NODE_TIMEOUT value?

Pupil_1 — Wed, 16 Aug 2006 14:13:48 GMT

changes to the cluster.ascii will need a cmapplyconf and copy the binary to the other node to take effect !!
This will need a cluster service restart.

Re: NODE_TIMEOUT value?

melvyn burnard — Wed, 16 Aug 2006 14:20:22 GMT

The NODE_TIMEOUT and HERTBEAT_INTERVAL are all in microseconds, so yes this is 6 seconds
To make the change, edit your ascii file and change the value, then halt the cluster, and use cmapplyconf to reapply the binary with the new value.

Re: NODE_TIMEOUT value?

dictum9 — Wed, 16 Aug 2006 14:46:40 GMT

Thanks, it's exactly what I was looking for.

Re: NODE_TIMEOUT value?

Steven E. Protter — Wed, 16 Aug 2006 15:12:48 GMT

Shalom etc,

If you are planning on changing this value, caution is urged.

Most SG guides do have this figure increased a bit from the default to avoid unneeded TOC and boots of nodes.

But increasing it bears risks that your cluster response to real problems will be increased as well.

SEP

Re: NODE_TIMEOUT value?

Jeff Schussele — Wed, 16 Aug 2006 15:38:58 GMT

This value should always be determined by 2 factors:

1) The avg latency of the network you employ as the heartbeat path - too high & you'll get unnecessary TOCs as SEP pointed out. We *always* use private nets with our own switches - you should too. We aaaalllll know that our public networks are light-speed & bullet-proof....right?????

2) The "urgency" your enterprise needs to get that pkg over to the adoptive node (notice how I've changed the term from failover - that latter word is now a no-no for us &~() )

In the end 8 seconds *should* be fine for 99% of clusters. I never have had to change it. And I don't see 6 as an issue either. Jeeeez if you can't get a low-level stack packet to your neighbor in 6 seconds you have bigger issues.....

My $0.02,
Jeff

Re: NODE_TIMEOUT value?

dictum9 — Thu, 17 Aug 2006 08:04:57 GMT

This makes it most clear. Thank you.