|
|
Sponsored Content
Operating Systems
HP-UX
MC ServiceGaurd
Post 4927 by alwayslearningunix on Friday 3rd of August 2001 05:23:39 PM
08-03-2001
MC ServiceGuard is still at the forefront of HP-UX's high availability software, it has been developed to the point where (providing hardware behaves itself) it can provide 99.999% availability when spreading a service across two service guarded machines.
It's quite a sophisticated product, providing a double heartbeat between nodes to monitor machine availability in a cluster and has a whole host of cluster wide and node specific configurable parameters - HP's course covers 5 days. It works from the entry level A class server through to the top end Superdome, as well as on workstations (although the reasoning behind it's application there would be somewhat baffling).
The product does not pretend to create fault tolerant machines, I think fault tolerance in the strict sense of the word is something yet to be attained on servers, and the domain of the mainframe - but it does guarantee high availibilty and with most service level agreements providing for scheduled maintenence downtime a high availability cluster that is service guarded can provide a near fault tolerant environment by allowing services to be flipped from node to node as the sectrions of the cluster is worked on for maintenance.
It's a great product, I would recommend learning it. I am on the course next week
Regards.
It's quite a sophisticated product, providing a double heartbeat between nodes to monitor machine availability in a cluster and has a whole host of cluster wide and node specific configurable parameters - HP's course covers 5 days. It works from the entry level A class server through to the top end Superdome, as well as on workstations (although the reasoning behind it's application there would be somewhat baffling).
The product does not pretend to create fault tolerant machines, I think fault tolerance in the strict sense of the word is something yet to be attained on servers, and the domain of the mainframe - but it does guarantee high availibilty and with most service level agreements providing for scheduled maintenence downtime a high availability cluster that is service guarded can provide a near fault tolerant environment by allowing services to be flipped from node to node as the sectrions of the cluster is worked on for maintenance.
It's a great product, I would recommend learning it. I am on the course next week
Regards.
|
|
LEARN ABOUT DEBIAN
condor_suspend
condor_suspend(1) General Commands Manual condor_suspend(1) Name condor_suspend suspend - jobs from the Condor queue Synopsis condor_suspend [-help -version] condor_suspend[-debug] [-pool centralmanagerhostname[:portnumber]-name scheddname][-addr "<a.b.c.d:port>"] cluster cluster.process user -constraint expression-all Description condor_suspendsuspends one or more jobs from the Condor job queue. If the -nameoption is specified, the named condor_scheddis targeted for processing. Otherwise, the local condor_scheddis targeted. The job(s) to be suspended are identified by one of the job identifiers, as described below. For any given job, only the owner of the job or one of the queue super users (defined by the QUEUE_SUPER_USERS macro) can suspend the job. Options -help Display usage information -version Display version information -pool centralmanagerhostname[:portnumber] Specify a pool by giving the central manager's host name and an optional port number -name scheddname Send the command to a machine identified by scheddname -addr <a.b.c.d:port> Send the command to a machine located at "<a.b.c.d:port>" -debug Causes debugging information to be sent to stderr , based on the value of the configuration variable TOOL_DEBUG cluster Suspend all jobs in the specified cluster cluster.process Suspend the specific job in the cluster user Suspend jobs belonging to specified user -constraint expression Suspend all jobs which match the job ClassAd expression constraint -all Suspend all the jobs in the queue Exit Status condor_suspendwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure. Examples To suspend all jobs except for a specific user: % condor_suspend -constraint 'Owner =!= "foo"' Author Condor Team, University of Wisconsin-Madison Copyright Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0. See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu September 2012 condor_suspend(1)