Skip to content
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.

Cyclic replication networks #116

Closed
krasserm opened this issue Oct 7, 2015 · 1 comment
Closed

Cyclic replication networks #116

krasserm opened this issue Oct 7, 2015 · 1 comment
Assignees
Milestone

Comments

@krasserm
Copy link
Contributor

krasserm commented Oct 7, 2015

For example, given three locations A, B and C, it should be able to connect them like:

 A --- C
  \   /
    B

With a replication network that may contain cycles, a location failure doesn't necessarily lead to a partition any more. Also, if the replication connection between A and B is broken, for example, due to a network failure, A and B can continue to exchange events via C.

So far, event replication recorded a replication trace (= position history) to drive event replication in a replicated event log. Replication traces will not be recorded any more and replication will be based on causality criteria (and additional custom replication filters if configured by an application). This is an important prerequisite for #106, #107 and #142.

Replication based on causality criteria in cyclic replication networks still ensures that local event logs are valid linear extensions of the happened-before relation of events.

@krasserm krasserm added this to the 0.4 milestone Oct 7, 2015
@krasserm krasserm self-assigned this Oct 7, 2015
@krasserm krasserm changed the title Use only causality criteria for event replication Support cyclic replication networks Oct 11, 2015
@krasserm krasserm modified the milestones: 0.4, 0.4-M1 Oct 11, 2015
@krasserm krasserm changed the title Support cyclic replication networks Cyclic replication networks Oct 11, 2015
@krasserm
Copy link
Contributor Author

Closed with 9a2d4e5

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant