Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
This chapter is from the book

Gathering Application Information

Once you have determined that an application suits the cluster environment, and have determined exactly what the scope of the project will be, the next step is to gather information about the application so that you can start to build the associated resource type. At the most fundamental level, this means you will need to determine exactly how to start, stop, and monitor the application automatically.


Determining how to start the application is the most important part of developing an agent, since it is the only part of the process that the cluster framework cannot handle by itself. You should keep in mind that starting an application doesn't just mean knowing the path to the program, but often includes a number of other components, for example:

  • Command-line arguments
  • Configuration files
  • Environment variables
  • User
  • Timeout

If there is a chance of multiple instances of an application running on the same cluster, it is particularly important to pay attention to the command-line arguments and configuration files that must be used to differentiate between these instances. These variable items might then be turned into extension properties of the final resource type (see Chapter 6), so that an administrator can control these aspects of the application when configuring the cluster.

In some cases it may be necessary to write a wrapper script to start an application with the correct set of configuration variables, and this is especially true if an application must be started as a particular user other than "root." For Solaris applications that normally start at boot time, there may already be an appropriate script in the /etc/init.d directory that you can use directly or modify slightly to have the required effect. Remember that if you add an application to the cluster that is normally started at boot time, you should remove the original start and stop script(s) from the /etc/rc?.d directories.

The amount of time taken for your application to start is also important. By default, the cluster framework will wait 300 seconds (five minutes) for the application to start up before sending the first probe to check that everything is okay. If your application takes longer than this to start, then you will have to change this delay when creating the agent.

Finally, you should make a note of anything that your application depends upon, including the presence of particular data or filesystems, networks, or other applications. It may be that in order to make one application highly available, others will need to be made highly available as well. If your application depends on another, you can add to the startup code for your agent check for the availability of that service. You should also document this dependency so that administrators can configure the cluster framework appropriately so that applications start in the correct order.

Most applications start after the network has started, but in some cases it may be important to start (or partially start) applications before the network has been configured. As we will see later in the book, the cluster framework allows us to run actions before and after the network has been started, so it is important to make a note of what your application expects to happen and when.


Stopping your application correctly is important to ensure data integrity when the service is failed over to another node. Not every failover occurs as a result of a system crash, so knowing how to stop gracefully is a vital part of the agent software.

In many cases, it is possible to safely stop an application simply by sending a TERM signal to the running process. In fact if you do not specify a particular program to stop your application, the cluster framework will do this by default. However, if there is a program supplied with your application that can gracefully stop it, then it should be used.

As with starting an application, there are other factors to consider than just the command name, including:

  • Arguments, environment, and user
  • Timeout
  • Effects of kill(1)
  • When to stop

The arguments, environment, and user factors are the same as for starting an application (see "Start" earlier in this chapter), and the timeout is similar. As with starting the application, stopping the application is by default given 300 seconds (five minutes) to be successful.

The effects of kill(1) on the application are important because if, when creating an agent using the SunPlex Agent Builder or Generic Data Service (GDS) tools [2] you don't supply a specific command to stop your application, the cluster framework will use kill(1) by default. About 80 percent of the timeout will be used to send the TERM signal, and about 15 percent to send the KILL signal. Even if you do provide a stop command (using one of the tools or not), the timeout value you supply will be used to decide how long the cluster framework will wait for an application to stop before deciding that something has gone wrong. As with the start timeout value, the default stop timeout is 300 seconds.

You should also consider whether the application should be stopped before or after the public network connection is removed. In most cases the application will be stopped before the network connection, but there may be times when you want to be sure that the network has been removed before stopping the application. However, this would normally be the case only when your application doesn't use the network directly.


Understanding how an application works is key to integrating it into the cluster environment. Once you have worked out how an application will behave under various conditions, you can create a monitor program that will check for these conditions and return appropriate values to the cluster framework, which in turn are used to decide what actions if any should be taken by the cluster.

By default, no monitoring is done by the cluster framework. However, if you use one of the provided tools [3] to create a network-aware resource type, a simple service probe is automatically provided. This probe just attempts to connect to the service's IP address and port, and if successful assumes that the application is operating correctly. Obviously, most applications require more complex monitoring than this, and Sun Cluster allows you to create very sophisticated monitoring applications to return different fault and failure modes to the cluster framework.

When you create a monitor program, you are in effect creating a type of expert system, in which a piece of software performs the tasks that might otherwise need to be done by a human operator. For this reason, detailed analysis of the application flow and possible failure modes will aid in the development of your resource type.

One way of tracking what your monitor program must do to check that your application is running correctly is to use a flowchart like that shown in Figure 4.3. In this example, we start by having the monitor program request a known piece of information from the application. If the request times out without any response, then the monitor program will check to see if the cluster framework is controlling the application properly, and take appropriate actions. If the request for data is successful, then the monitor program will compare the response from the application to what it expects the response to be: If they are the same, then the monitor will assume that everything is okay, and will go to sleep for a while before starting the whole process again. If the data received from the application is not what the monitor program expected, then it will check to see if any data was received and take appropriate action, which may be to send a warning to human operators or to restart or even fail over the application.


Figure 4.3 Application monitoring flowchart

As you can see, it is very important to understand how your application behaves before you can write a successful monitoring program. In some cases, the application you are trying to make highly available may already have a program you can use to check the status. In such situations, you simply need to ensure that the program will return zero if the application is okay, and 1 (or nonzero) if there is a problem. In other cases, you may require quite complex programming to assess the state of the application and decide what action to take, particularly if you want to take very specific actions when certain events (such as network failures, for example) occur. The Sun Cluster APIs provide the tools to retrieve a lot of information about the cluster environment itself, but it is your understanding of the application that will determine how successful your monitor program will be.

As with starting and stopping an application, running the monitor program may require specific command-line arguments and environment variables, need a particular user ID, and require a certain amount of time to run. These factors need to be documented so that you can integrate them into your resource type.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020