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

Disaster recovery enhancements #286

Closed
krasserm opened this issue Jul 4, 2016 · 0 comments
Closed

Disaster recovery enhancements #286

krasserm opened this issue Jul 4, 2016 · 0 comments
Assignees
Milestone

Comments

@krasserm
Copy link
Contributor

krasserm commented Jul 4, 2016

  • Separate metadata recovery from event recovery
  • Eventuate-internal state should be recoverable from metadata alone
  • Optional recovery from filtered replication connections
@krasserm krasserm added this to the 0.8 milestone Jul 4, 2016
@krasserm krasserm added the ready label Jul 4, 2016
volkerstampa added a commit that referenced this issue Sep 9, 2016
- start event recovery from filtered connections *after* event recovery
  from unfiltered connections is finished
- test recovery over filtered/unfiltered connections

- closes #286
volkerstampa added a commit that referenced this issue Sep 9, 2016
- start event recovery from filtered connections *after* event recovery
  from unfiltered connections is finished
- test recovery over filtered/unfiltered connections

- closes #286
@volkerstampa volkerstampa self-assigned this Sep 12, 2016
volkerstampa added a commit that referenced this issue Sep 19, 2016
- use dedicated message for resetting remote replication progress
- replace println progress logging by using akka-log
- add tests for
  - recovery after upgrade
  - simultaneous recovery
- start event recovery from filtered connections *after* event recovery
  from unfiltered connections is finished
- test recovery over filtered/unfiltered connections
- adjust local sequence nr when receiving replicated events
- remove sequence no gap detection as there might be gaps in case of
  incomplete disaster recovery

- closes #286
volkerstampa added a commit that referenced this issue Sep 19, 2016
- use dedicated message for resetting remote replication progress
- replace println progress logging by using akka-log
- add tests for
  - recovery after upgrade
  - simultaneous recovery
- start event recovery from filtered connections *after* event recovery
  from unfiltered connections is finished
- test recovery over filtered/unfiltered connections
- adjust local sequence nr when receiving replicated events
- remove sequence no gap detection as there might be gaps in case of
  incomplete disaster recovery

- closes #286
volkerstampa added a commit that referenced this issue Sep 20, 2016
- use dedicated message for resetting remote replication progress
- replace println progress logging by using akka-log
- add tests for
  - recovery after upgrade
  - simultaneous recovery
- start event recovery from filtered connections *after* event recovery
  from unfiltered connections is finished
- test recovery over filtered/unfiltered connections
- adjust local sequence nr when receiving replicated events
- remove sequence no gap detection as there might be gaps in case of
  incomplete disaster recovery

- closes #286
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

2 participants