@InProceedings{qin05rx,
  author    = {Qin, Feng and Tucek, Joseph and Sundaresan, Jagadeesan and Zhou, Yuanyuan},
  booktitle = {Proceedings of the twentieth ACM symposium on Operating systems principles},
  date      = {2005},
  title     = {Rx: treating bugs as allergies---a safe method to survive software failures},
  pages     = {235--248},
  comment   = {* context: generic recovery from software bugs
* approach: rollback and re-execution with modified environment upon
  error
* observation/statement that many bugs are triggered by environment

  * diverse references/citations regarding types of software failures
  * categorize approaches to survive software failures

    * micro-/reboot / software-rejuvenation
    * checkpoint, rollback, re-execute
    * application-specific approaches

      * e.g., exception handling, multiple processes

    * non-conventional approaches

* not much details on checkpoint-and-rollback component

  * handles memory state, files, file pointers

* implement wrappers for functions which access the environment

  * malloc, IO incl. network system calls, scheduling, IPC, process
    signaling, etc.
  * modify environment during re-execution via such wrappers

* a lot of text/work regarding checkpoint management
* a proxy to handle failures during communication

  * e.g., so client requests can be replayed in a series of HTTP
    requests

* detailed discussion on implementation limitations

  * checkpoints for multi-threaded applications
  * in distributed systems, all nodes should use their tool, which
    should then also be coordinated (e.g., checkpoint and rollback
    distributed state)

* case study on MySQL, Squid, Apache and CVS servers},
  file      = {:qin05rx - Rx_ treating bugs as allergies---a safe method to survive software failures.pdf:PDF},
  groups    = {dependability by default / dependability wrap},
  timestamp = {2021-08-30},
}

{"_id":"8ZLNdzindd7cSnkFv","bibbaseid":"qin-tucek-sundaresan-zhou-rxtreatingbugsasallergiesasafemethodtosurvivesoftwarefailures","authorIDs":[],"author_short":["Qin, F.","Tucek, J.","Sundaresan, J.","Zhou, Y."],"bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"propositions":[],"lastnames":["Qin"],"firstnames":["Feng"],"suffixes":[]},{"propositions":[],"lastnames":["Tucek"],"firstnames":["Joseph"],"suffixes":[]},{"propositions":[],"lastnames":["Sundaresan"],"firstnames":["Jagadeesan"],"suffixes":[]},{"propositions":[],"lastnames":["Zhou"],"firstnames":["Yuanyuan"],"suffixes":[]}],"booktitle":"Proceedings of the twentieth ACM symposium on Operating systems principles","date":"2005","title":"Rx: treating bugs as allergies—a safe method to survive software failures","pages":"235–248","comment":"* context: generic recovery from software bugs * approach: rollback and re-execution with modified environment upon error * observation/statement that many bugs are triggered by environment * diverse references/citations regarding types of software failures * categorize approaches to survive software failures * micro-/reboot / software-rejuvenation * checkpoint, rollback, re-execute * application-specific approaches * e.g., exception handling, multiple processes * non-conventional approaches * not much details on checkpoint-and-rollback component * handles memory state, files, file pointers * implement wrappers for functions which access the environment * malloc, IO incl. network system calls, scheduling, IPC, process signaling, etc. * modify environment during re-execution via such wrappers * a lot of text/work regarding checkpoint management * a proxy to handle failures during communication * e.g., so client requests can be replayed in a series of HTTP requests * detailed discussion on implementation limitations * checkpoints for multi-threaded applications * in distributed systems, all nodes should use their tool, which should then also be coordinated (e.g., checkpoint and rollback distributed state) * case study on MySQL, Squid, Apache and CVS servers","file":":qin05rx - Rx_ treating bugs as allergies—a safe method to survive software failures.pdf:PDF","groups":"dependability by default / dependability wrap","timestamp":"2021-08-30","bibtex":"@InProceedings{qin05rx,\n author = {Qin, Feng and Tucek, Joseph and Sundaresan, Jagadeesan and Zhou, Yuanyuan},\n booktitle = {Proceedings of the twentieth ACM symposium on Operating systems principles},\n date = {2005},\n title = {Rx: treating bugs as allergies---a safe method to survive software failures},\n pages = {235--248},\n comment = {* context: generic recovery from software bugs\n* approach: rollback and re-execution with modified environment upon\n error\n* observation/statement that many bugs are triggered by environment\n\n * diverse references/citations regarding types of software failures\n * categorize approaches to survive software failures\n\n * micro-/reboot / software-rejuvenation\n * checkpoint, rollback, re-execute\n * application-specific approaches\n\n * e.g., exception handling, multiple processes\n\n * non-conventional approaches\n\n* not much details on checkpoint-and-rollback component\n\n * handles memory state, files, file pointers\n\n* implement wrappers for functions which access the environment\n\n * malloc, IO incl. network system calls, scheduling, IPC, process\n signaling, etc.\n * modify environment during re-execution via such wrappers\n\n* a lot of text/work regarding checkpoint management\n* a proxy to handle failures during communication\n\n * e.g., so client requests can be replayed in a series of HTTP\n requests\n\n* detailed discussion on implementation limitations\n\n * checkpoints for multi-threaded applications\n * in distributed systems, all nodes should use their tool, which\n should then also be coordinated (e.g., checkpoint and rollback\n distributed state)\n\n* case study on MySQL, Squid, Apache and CVS servers},\n file = {:qin05rx - Rx_ treating bugs as allergies---a safe method to survive software failures.pdf:PDF},\n groups = {dependability by default / dependability wrap},\n timestamp = {2021-08-30},\n}\n\n","author_short":["Qin, F.","Tucek, J.","Sundaresan, J.","Zhou, Y."],"key":"qin05rx","id":"qin05rx","bibbaseid":"qin-tucek-sundaresan-zhou-rxtreatingbugsasallergiesasafemethodtosurvivesoftwarefailures","role":"author","urls":{},"metadata":{"authorlinks":{}},"downloads":0,"html":""},"bibtype":"inproceedings","biburl":"https://bibbase.org/network/files/AsPiHTmHHGjgy6xSQ","creationDate":"2020-07-02T22:41:19.098Z","downloads":0,"keywords":[],"search_terms":["treating","bugs","allergies","safe","method","survive","software","failures","qin","tucek","sundaresan","zhou"],"title":"Rx: treating bugs as allergies—a safe method to survive software failures","year":null,"dataSources":["DXuKbcZTirdigFKPF","wjZw5s4JL49uLwn3p"]}