topic Re: Should package stay on the primary or adoptive node? in Operating System - HP-UX

Should package stay on the primary or adoptive node?

Hanry Zhou — Fri, 18 Nov 2005 16:05:15 GMT

We are going to convert a production node to be a 2-nodes cluster. So, one new node will be added in as the adoptive node.

Now, assume the SG is successfuly implemented on the 2-nodes cluster. My question is: what is your consideration would be in terms of which node the package should be stay on? should I put the package on the primary node (the previous one node production server), or should I let the package stay on the adoptive node for a few days, and therefore the package working on the new added node could be more matured?

Re: Should package stay on the primary or adoptive node?

A. Clay Stephenson — Fri, 18 Nov 2005 16:12:35 GMT

Considering that most hardware failures (especially disk drives) occur at the beginning of life and end of life (think of a bathtub shaped curve), I would run the package on what you calling your primary node. The hardware-related failures will occur whether or not the package is running so the idea is that the machine that is most likely to fail over the next few days is the one you want to avoid causing real harm to the package. You should, of course, allow the package to failover to the adoptive node but once you have passed that test, I would return it to your old box.
It does make sense to keep both servers patched exactly the same and tuned the same.

Re: Should package stay on the primary or adoptive node?

Bharat Katkar — Sat, 19 Nov 2005 03:27:29 GMT

Hi,
If you are to choose between the nodes for package to run i would obviously go for the most reliable and proven machine performance being the another aspect.

You should go for primary no doubt but if you are very sure the adoptive node is more capable, stable and performance wise better than the primary one then it should not actually matter to run the package on adoptive node.

Since it was already running on primary (assuming it had no issues at all) i would prefer the same in future also.

Regards,

Re: Should package stay on the primary or adoptive node?

Steven E. Protter — Sat, 19 Nov 2005 15:37:58 GMT

I recommend going for active node on the reliable, proven node.

Another consideration though. If the newly added node has more memory or a faster processor or other benefits, you might not want to follow that advice.

Its a business decision taking into account facts you have not fully presented here.

SEP

Re: Should package stay on the primary or adoptive node?

Sยภเl Kย๓คг — Sat, 19 Nov 2005 22:41:29 GMT

Hi,
How old is your current production server. If it's purchased recently and you are planning to go for a same hardware with same config, better you keep ur primary node as the current one, 'Known devil is better than an unknown god!'

If you are planning to go for a machine with higher config and obiously more reliable one, better to run the pkg on that.

More over it is recommended that, u switch the package between the servers once in a quarter on like.

Regards,
Sun