THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
| Raft | PacificA | |
|---|---|---|
| Availability conditions | A majority of the group must be online to make progress | Can make progress even with one member left |
| Dependencies | Independent | Requires external consistent configuration manager |
| Latency | Can acknowledge an operation after a majority of the group responded | Must await responses from either all group members or wait for failure detection timeout and reconfigure the group before acknowledging an operation |
| Other | Relies on clock timeouts to ensure linearizability of operations |
Group Membership
Besides metastorage itself, Ignite will need a group membership/discovery service with likely less strict consistency guarantees than the current Discovery SPI. The membership service will be used (not limited to):
- Discover and automatically form an initial metastorage Raft replication group
- Provide cluster membership changes events for subsystems that do not require strict consistency guarantees (Compute grid, SQL query execution runtime, etc).
The requirements for these subsystems should be carefully examined to choose a proper cluster membership protocol. The alternatives we currently have are:
- SWIM [3], an eventually-consistent protocol widely used by multiple systems, with Java implementation available [4].
- RAPID [5], a novel consistent group membership protocol, with Java implementation also available [6].
Further Applications
Partition Replication
...
Overview
Content Tools
Apps