Some consequences of excess load on the Echo replicated file system

Abstract

Understanding the workload is crucial for the success of a replicated file system. The system must continue to provide service in the presence of excess load, otherwise, its availability will be compromised. This paper presents some shortcomings of the Echo replicated file system in handling excess load. The authors discuss the consequences of excess load on primary secondary design, on their communication software, on election algorithm, on memory usage in their file servers, and on their distributed client caching algorithm. They speculate on possible solutions.<>