AntidoteDB
  • Overview
  • Quickstart
  • Examples & Applications
    • Timeseries Load Generator
    • Antidote Web Shell
    • Calendar App
    • Todo List App
  • Tutorials
    • Java Tutorial
  • Related Projects
  • Architecture
    • Overview
    • Ring
    • Log
    • Materializer
    • Transaction Manager
    • Inter-DC Communication
    • Failure Modes
    • Datatypes in Antidote
    • Commit Hooks
    • Features Configuration
  • Deployment
    • Natively (Linux)
    • Local Docker Setup
    • Docker Compose Setups
    • Docker Swarm
    • Kubernetes
  • Monitoring
    • Prometheus and Grafana
  • API
    • Native (Erlang)
    • Protocol Buffer API
    • Erlang
    • Java
    • JavaScript
    • Go
    • Python
  • Benchmarking
    • Setup
    • Basho Bench
  • Tools
    • Logs and Cache Dump
  • Development
    • Setup & Environment
    • Building a Release
    • Testing
    • Contributing
    • Archived Works
  • Release Notes
    • 0.2.1
    • 0.1.1
    • 0.0.1
Powered by GitBook
On this page
  • Supported
  • DC Death / Network Partition
  • Shard Death
  • Unsupported
  • Process Death
  1. Architecture

Failure Modes

Supported

DC Death / Network Partition

Currently the fault type supported by Antidote is only killing an entire DC, then restarting it will load the state back from disk and restart all connections .

Shard Death

If a shard inside a DC crashes, it restarts and fetches missing updates from a remote DC.

Unsupported

Process Death

If a single process within the node dies and restarts it is not guaranteed that the state is loaded correctly (see Issue #218 and Issue #193).

PreviousInter-DC CommunicationNextDatatypes in Antidote

Last updated 5 years ago