Tags: skielosky/cadence
Tags
Update docker image with latest cadence release (cadence-workflow#614) Fix config template to include new required config changes to bring up the Cadence server.
Revert "history service should do event reordering making sure corres… …ponding … (cadence-workflow#601)" (cadence-workflow#611) This reverts commit 6164b73.
bugfix: parent workflow, when signaling child workflow, can experienc… ( cadence-workflow#607) * bugfix: parent workflow, when signaling child workflow, can experience deadlock, if child workflow, at the same time, is completed. * bugfix: handling workflow using decision to cancel itself.
TimerQueueProcessor stuck fix on large backlog on available timers (c… …adence-workflow#460) TimerQueueProcessor issues a query to DB for visibilityTime '>=' from the readlevel. This could result in reading same timer multiple times and trips the processor in thinking it fired all available timers as the number of tasks returned back to the caller would be less than batch size. Updated the logic to return an explicit flag back to the caller so it can immediately callback again when there are more timers to fire. fixes cadence-workflow#461.
This release has a lot of new features and some important stability f… …ixes for known Cadence server issues. This release also includes few schema changes to both cadence and visibility keyspaces. It is required to deploy schema version 0.2 of cadence and visibility keyspaces before deploying this release. This tag version update includes schema version updates in docker scripts.
Create a single connection pool per host (cadence-workflow#359) When history service comes up it creates a gocql client for execution manager and then uses the same client for all shards for making persistence calls. Also created config knobs to configure number of connections for both events and execution manager clients. Also include shard tag for shard manager calls. fixes cadence-workflow#307
PreviousNext