I/O bound computing clusters Post: 302691811

9 More Discussions You Might Find Interesting

1. High Performance Computing

question about clusters

hello all...first off let me say hi and im really glad to be apart of this community....tried to join awhile back but i couldnt for some reason im a highschool student and im eager to learn and what im trying to learn now is clusters i have 3 computers in my room all connected on a simple hub ...

2. Virtualization and Cloud Computing

Event Cloud Computing - IBM Turning Data Centers Into ?Computing Cloud?

Tim Bass Thu, 15 Nov 2007 23:55:07 +0000 *I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing...

3. Solaris

List zones bound to a pool

How to get the list of zones which are bound to a pool say appPool. Rather then logging in each zone and then check from pool stat command.

4. Programming

env not bound: BEDEWORK

I was trying to test dump data on bedework jxi console however I got the error below.I'm using debian as my OS and installed quickstart bedework on it. Pls advise what am I missing. thanks Caused by: javax.naming.NameNotFoundException: env not bound at...

5. Solaris

VCS Clusters

:)Hi, can someone please explain VCS clustering and where do we need VCS clusters ..? :o:)Thanks in advance :o:)

6. Linux

Memory bound error...

Hi all, Am getting the below error for a job that is run in our system. error code: 114, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 11) This job uses a cobol program and as far as I know, the problem is related to this cobol program. What does this...

7. Solaris

Bound, Unbound, Idle, Listening,

Hi Guys, I am studying netstat and I am getting confused a lot. I will be glad if someone will be kind enough to explain to me : 1) bound port 2) unbound port 3) idle 4 listening I will very much appreciate it. Thanks guys We have a special forum with special rules for homework

8. Emergency UNIX and Linux Support

How to fix the CPU bound issues on AIX?

Hi All, Can you please answer my question. i see lot of CPU utilization on AIX LPARs. i am able to find the cause of the probelm. But i do not know how to mitigate or fix the problem. for instance, i found the process which is consuming most of CPU. i informed the responsible team. how...

9. Shell Programming and Scripting

Awk: get upper and lower bound per group

Hi all, I've data as: 22 51018157 51018157 exonic CHKB nonsynonymous SNV 22 51018204 51018204 exonic CHKB nonsynonymous SNV 22 51018428 51018428 exonic CHKB nonsynonymous SNV 22 51018814 51018814 ...

LEARN ABOUT HPUX

cmhaltnode

cmhaltnode(1m)															    cmhaltnode(1m)

NAME

       cmhaltnode - halt a node in a high availability cluster

SYNOPSIS

       cmhaltnode [-f] [-v] [-t] [node_name...]

DESCRIPTION

       cmhaltnode causes a node to halt its cluster daemon and remove itself from the existing cluster.

       To halt cluster on the node, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configu-
       ration file. See access policy in cmquerycl.

       When cmhaltnode is run on a node, the cluster daemon is halted and, optionally, all packages that were running on that node  are  moved	to
       other nodes if possible.

       If node_name is not specified, the cluster daemon running on the local node will be halted and removed from the existing cluster.

       If  you issue this command while a cluster is still in the process of forming, the command will fail with the message "Unable to connect to
       daemon."  If this happens, wait for the cluster to form successfully, then issue the command again.

   Options
       cmhaltnode supports the following options:

	      -f	Force the node to halt even if there are packages or group members running on it.  The group members on the node  will	be
			terminated.   The halt scripts for all packages running on the node will be run; based on priority or dependency relation-
			ships, this may affect packages on other nodes. In other words, packages on other nodes may either start or halt based	on
			this  package halting.	If the package configuration and current cluster membership permit, and if the package halt script
			succeeds, the packages will be started on other nodes.	Without this option, if packages are running on  the  given  node,
			the command will fail.	If a package fails to halt, the node halt will also fail.

	      -v	Verbose output will be displayed.

	      -t	Test  only.  Provide  an assessment of the package placement without affecting the current state of the nodes or packages.
			This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies
			such as EMS resources, package subnets, and storage before predicting any package placement decisions. If there is a pack-
			age in maintenance mode running on the nodes being halted, the package will always be halted and not failover  to  another
			node; the report will not display an assessment for that package.

	      node_name...
			The name of the node(s) to halt.

RETURN VALUE

       cmhaltnode returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Halt the cluster daemon on two other nodes:

	      cmhaltnode node2 node3

AUTHOR

       cmhaltnode was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					    cmhaltnode(1m)