On Misbehaviour and Fault Tolerance in Machine Learning Systems

TL;DR

This paper investigates fault tolerance in ML systems, highlighting common design patterns and emphasizing the need for mature engineering practices to improve reliability and security in adaptive ML applications.

Contribution

It provides a conceptual framework for understanding ML misbehaviour, identifies emerging fault-tolerant design patterns, and underscores the field's immaturity and need for further development.

Findings

Monitoring input data and outputs for fault detection

Using multiple models and fallback strategies for robustness

Design patterns are emerging but not yet widely adopted

Abstract

Machine learning (ML) provides us with numerous opportunities, allowing ML systems to adapt to new situations and contexts. At the same time, this adaptability raises uncertainties concerning the run-time product quality or dependability, such as reliability and security, of these systems. Systems can be tested and monitored, but this does not provide protection against faults and failures in adapted ML systems themselves. We studied software designs that aim at introducing fault tolerance in ML systems so that possible problems in ML components of the systems can be avoided. The research was conducted as a case study, and its data was collected through five semi-structured interviews with experienced software architects. We present a conceptualisation of the misbehaviour of ML systems, the perceived role of fault tolerance, and the designs used. Common patterns to incorporating ML components in design in a fault tolerant fashion have started to emerge. ML models are, for example, guarded by monitoring the inputs and their distribution, and enforcing business rules on acceptable outputs. Multiple, specialised ML models are used to adapt to the variations and changes in the surrounding world, and simpler fall-over techniques like default outputs are put in place to have systems up and running in the face of problems. However, the general role of these patterns is not widely acknowledged. This is mainly due to the relative immaturity of using ML as part of a complete software system: the field still lacks established frameworks and practices beyond training to implement, operate, and maintain the software that utilises ML. ML software engineering needs further analysis and development on all fronts.