diff options
| author | cnnrznn <cnnrznn@gmail.com> | 2016-12-08 13:46:32 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-12-08 13:46:32 -0500 |
| commit | f9b1bc6f8747e1e73f516cce278cc3a4708d75f0 (patch) | |
| tree | 41b39b627021bc2e93a5a56cc91f3f8fcf838feb /chapter/4 | |
| parent | e136271f9041c8a565383f616a331875b7617dc0 (diff) | |
Update dist-langs.md
Diffstat (limited to 'chapter/4')
| -rw-r--r-- | chapter/4/dist-langs.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/chapter/4/dist-langs.md b/chapter/4/dist-langs.md index 098c87b..785d2b7 100644 --- a/chapter/4/dist-langs.md +++ b/chapter/4/dist-langs.md @@ -13,7 +13,7 @@ In this section, we present an overview of these three problems and their impact ### Partial Failure -On a single-machine environment, a crash means that either the machine has failed (total failure), or the source of the crash can be learned from a central resource manager such as the operating system. (// TODO cite "a note on dist. comp.) +In the case of a crash on a local environment, either the machine has failed (total failure), or the source of the crash can be learned from a central resource manager such as the operating system. (// TODO cite "a note on dist. comp.) If an application consists of multiple communicating processes partial failure is possible, however because the cause of the partial failure can be determined, this kind of partial failure can be repaired given the operating system's knowledge about the failure. For example, a process can be restored based on a checkpoint, another process in the application can query the operating system about another's state, etc. |
