On the analysis of software rejuvenation policies

Sachin Garg, M. Telek, Antonio Puliafito, Kishor S. Trivedi

Research output: Chapter in Book/Report/Conference proceedingConference contribution

15 Citations (Scopus)

Abstract

Software rejuvenation is a technique for software fault tolerance which involves occasionally stopping the executing software, `cleaning' the `internal state' and restarting. This cleanup is done at desirable times during execution on a preventive basis so that unplanned failures, which result in higher costs compared to planned stopping, are avoided. Since during rejuvenation, the software is typically unavailable or in a degraded mode of operation, the operation involves a cost. In this paper, we present an analytical model of a software system which serves transactions. Due to `aging', not only the service rate of the software decreases with time but the software itself experiences occasional crash/hang failures. We propose and compare two rejuvenation policies. The policies are evaluated for the resulting steady state availability as well the probability that a transaction is denied service. We also numerically illustrate the use of our model to compute the optimal rejuvenation interval which minimizes (maximizes) the loss probability (steady state availability).

Original languageEnglish
Title of host publicationCOMPASS - Proceedings of the Annual Conference on Computer Assurance
Editors Anon
PublisherIEEE
Pages88-96
Number of pages9
Publication statusPublished - 1997
EventProceedings of the 1997 12th Annual Conference on Computer Assurance, COMPASS'97 - Gaithersburg, MD, USA
Duration: Jun 16 1997Jun 19 1997

Other

OtherProceedings of the 1997 12th Annual Conference on Computer Assurance, COMPASS'97
CityGaithersburg, MD, USA
Period6/16/976/19/97

Fingerprint

Availability
Fault tolerance
Costs
Analytical models
Cleaning
Aging of materials

ASJC Scopus subject areas

  • Hardware and Architecture

Cite this

Garg, S., Telek, M., Puliafito, A., & Trivedi, K. S. (1997). On the analysis of software rejuvenation policies. In Anon (Ed.), COMPASS - Proceedings of the Annual Conference on Computer Assurance (pp. 88-96). IEEE.

On the analysis of software rejuvenation policies. / Garg, Sachin; Telek, M.; Puliafito, Antonio; Trivedi, Kishor S.

COMPASS - Proceedings of the Annual Conference on Computer Assurance. ed. / Anon. IEEE, 1997. p. 88-96.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Garg, S, Telek, M, Puliafito, A & Trivedi, KS 1997, On the analysis of software rejuvenation policies. in Anon (ed.), COMPASS - Proceedings of the Annual Conference on Computer Assurance. IEEE, pp. 88-96, Proceedings of the 1997 12th Annual Conference on Computer Assurance, COMPASS'97, Gaithersburg, MD, USA, 6/16/97.
Garg S, Telek M, Puliafito A, Trivedi KS. On the analysis of software rejuvenation policies. In Anon, editor, COMPASS - Proceedings of the Annual Conference on Computer Assurance. IEEE. 1997. p. 88-96
Garg, Sachin ; Telek, M. ; Puliafito, Antonio ; Trivedi, Kishor S. / On the analysis of software rejuvenation policies. COMPASS - Proceedings of the Annual Conference on Computer Assurance. editor / Anon. IEEE, 1997. pp. 88-96
@inproceedings{377a802914824bda9e976ab5b75a1459,
title = "On the analysis of software rejuvenation policies",
abstract = "Software rejuvenation is a technique for software fault tolerance which involves occasionally stopping the executing software, `cleaning' the `internal state' and restarting. This cleanup is done at desirable times during execution on a preventive basis so that unplanned failures, which result in higher costs compared to planned stopping, are avoided. Since during rejuvenation, the software is typically unavailable or in a degraded mode of operation, the operation involves a cost. In this paper, we present an analytical model of a software system which serves transactions. Due to `aging', not only the service rate of the software decreases with time but the software itself experiences occasional crash/hang failures. We propose and compare two rejuvenation policies. The policies are evaluated for the resulting steady state availability as well the probability that a transaction is denied service. We also numerically illustrate the use of our model to compute the optimal rejuvenation interval which minimizes (maximizes) the loss probability (steady state availability).",
author = "Sachin Garg and M. Telek and Antonio Puliafito and Trivedi, {Kishor S.}",
year = "1997",
language = "English",
pages = "88--96",
editor = "Anon",
booktitle = "COMPASS - Proceedings of the Annual Conference on Computer Assurance",
publisher = "IEEE",

}

TY - GEN

T1 - On the analysis of software rejuvenation policies

AU - Garg, Sachin

AU - Telek, M.

AU - Puliafito, Antonio

AU - Trivedi, Kishor S.

PY - 1997

Y1 - 1997

N2 - Software rejuvenation is a technique for software fault tolerance which involves occasionally stopping the executing software, `cleaning' the `internal state' and restarting. This cleanup is done at desirable times during execution on a preventive basis so that unplanned failures, which result in higher costs compared to planned stopping, are avoided. Since during rejuvenation, the software is typically unavailable or in a degraded mode of operation, the operation involves a cost. In this paper, we present an analytical model of a software system which serves transactions. Due to `aging', not only the service rate of the software decreases with time but the software itself experiences occasional crash/hang failures. We propose and compare two rejuvenation policies. The policies are evaluated for the resulting steady state availability as well the probability that a transaction is denied service. We also numerically illustrate the use of our model to compute the optimal rejuvenation interval which minimizes (maximizes) the loss probability (steady state availability).

AB - Software rejuvenation is a technique for software fault tolerance which involves occasionally stopping the executing software, `cleaning' the `internal state' and restarting. This cleanup is done at desirable times during execution on a preventive basis so that unplanned failures, which result in higher costs compared to planned stopping, are avoided. Since during rejuvenation, the software is typically unavailable or in a degraded mode of operation, the operation involves a cost. In this paper, we present an analytical model of a software system which serves transactions. Due to `aging', not only the service rate of the software decreases with time but the software itself experiences occasional crash/hang failures. We propose and compare two rejuvenation policies. The policies are evaluated for the resulting steady state availability as well the probability that a transaction is denied service. We also numerically illustrate the use of our model to compute the optimal rejuvenation interval which minimizes (maximizes) the loss probability (steady state availability).

UR - http://www.scopus.com/inward/record.url?scp=0030685484&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0030685484&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:0030685484

SP - 88

EP - 96

BT - COMPASS - Proceedings of the Annual Conference on Computer Assurance

A2 - Anon, null

PB - IEEE

ER -