Notes - MIECT
Computação Distribuída
Notes - MIECT
Computação Distribuída
  • Computação Distribuída
  • Introduction / Architecture
    • Distributed Systems
    • Architecture
    • Middleware Organizations
    • Processes
    • Threads
    • Virtualization
    • Clients
    • Servers
    • Migration
  • Communications
    • OSI Model
    • Middleware Layer
    • Types of Communication
    • Remote Call Procedure (RPC)
    • Sockets
    • Application-level Multicasting
  • Naming
    • Names
    • Addresses
    • Identifiers
    • Naming Systems
      • Flat Naming
      • Structured Naming
    • Internet Domain Name System (DNS)
    • Attribute-based naming - LDAP
  • Coordination
    • Clocks
      • Synchronizing without UTC
    • Reference Broadcast Synchronization – RBS
    • Happened-Before Relation
      • Logical Clocks
      • Vector Clocks
    • Mutual Exclusion Algorithms
    • Election Algorithms
    • Distributed Events Correspondance
  • Consistency & Replication
    • Replication
    • Performance and Scalability
    • Client-centric models
    • Replicates
    • Unicasting vs. Multicasting
    • Continuous Consistency
    • Protocols
  • Flaw Tolerance
    • Dependability
    • Terminology
    • Confidence vs. Security
    • Halting failures
    • Redundancy to mask failures
    • Consensus
      • Realistic
      • Consensus in arbitrary failures
      • Achieving failure tolerance
      • Distributed consensus
    • Failure Detection
    • Reliable RPCs
    • Distributed commit protocols
  • Python asyncio & Friends
    • Async
    • Sync vs. Async
    • Tools
  • Flask
    • Introduction
    • Python Requests
  • Containers
    • VM's vs Containers
    • OS Support
    • Building a container
    • Tools
    • Portability
    • Docker
      • Container
  • Map Reduce
    • Map Recude
    • Hadoop
    • Software Architecture
    • Task Scheduling
    • Comparison With Traditional Models
  • Cloud Computing
    • Cloud Computing
    • IaaS – Infrastructure as a Service
    • PaaS – Platform as a Service
    • SaaS – Software as a Service
    • Business Models
Powered by GitBook
On this page
  • Types of redundancy
  • Process resilience
  • Groups and failure masks
  • K-fault tolerant group
  1. Flaw Tolerance

Redundancy to mask failures

PreviousHalting failuresNextConsensus

Last updated 1 year ago

Types of redundancy

  • Information: Add extra bits to the data units so that the errors can be recovered when the bits are damaged.

  • Temporal: Design the system in such a way that an action can be performed again in case of something wrong happens. Usually used when the failures are transient or intermittent.

  • Physical: Adding equipment or processes in such a way to allow that one or more components can fail. This is typically used in distributed systems.

Process resilience

Protecting against the malfunction of a process through the replication of processes, and organizing multiple processes in process groups. Distinguishing between plain groups and hierarchical groups.

Groups and failure masks

K-fault tolerant group

When a group can concurrently mask any failure of its members (k is the tolerance degree to failures).

How big does it need to be?

  • With terminal failures (crash/omission/temporal): we need k+1 members, and no member will produce an incorrect result provided that a single member is sufficient.

  • With arbitrary failures: we need 2k+1 members so that the correct result can be obtained by a majority of votes.

Important assumptions

  • All the members are equal.

  • All the members process the commands in the same order.

We need to be sure that all the processes do the same.