bloomberg / bloomberg/comdb2

how does comdb deal with partitions

Open
#647 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
1.5k
Forks
243
Avg merge
2d 2h
Merged PRs (30d)
37

Description

The paper doesnt say much. Only:

```
A node disconnected from a master
for a prolonged time (ie longer than lease) is unable to serve
any type of request. Further, a network partition leaving no
group as a majority results in a cluster with no master and
all nodes unable to serve any requests.
```

Lets say you have a cluster with 9 nodes.

a partition happens such that, the cluster gets separated into groups of:

1. 5 nodes
2. 3 nodes
3. 1 node

Now after a while of partitioning, each of these 3 clusters will think of themselves as largest and allow transactions over each one.

Once the partition goes, away and all 9 nodes can see each other, what happens to the transactions that were already committed in each of the separate 3 groups?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.