Skip to content

Commit

Permalink
Apply replication history events to passive cluster (#643)
Browse files Browse the repository at this point in the history
Created history replicator which is invoked by the replicator for
processing of history replication tasks.  It processes the history
events from the replication task and make mutable state updates for each
event.  Once all events are processed it commits the entire update using
the workflowContext API used by rest of the stack.

Also mutableStateBuilder changes to apply mutable state changes using
the actual event.  This required some refactoring of mutableStateBuilder
to reuse as much code as possible between replicator and rest of the
stack.

History service has new API ReplicateEvents which is called by the
replicator to apply history events.

Current this change only works for the happy case and is not guarded by
version updates on the domain.
Replicator does not support out of order processing of history
replication tasks.
  • Loading branch information
samarabbas authored Apr 2, 2018
1 parent 3e3e2fc commit fa74c62
Show file tree
Hide file tree
Showing 22 changed files with 1,487 additions and 75 deletions.
497 changes: 497 additions & 0 deletions .gen/go/history/historyservice_replicateevents.go

Large diffs are not rendered by default.

29 changes: 29 additions & 0 deletions .gen/go/history/historyserviceclient/client.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

37 changes: 36 additions & 1 deletion .gen/go/history/historyserviceserver/server.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

31 changes: 31 additions & 0 deletions .gen/go/history/historyservicetest/client.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions .gen/go/history/idl.go

Large diffs are not rendered by default.

Loading

0 comments on commit fa74c62

Please sign in to comment.