Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return ShardOwnershipLostError as catch all from persistence layer #873

Merged
merged 2 commits into from
Jun 21, 2018
Merged

Return ShardOwnershipLostError as catch all from persistence layer #873

merged 2 commits into from
Jun 21, 2018

Commits on Jun 21, 2018

  1. Return ShardOwnershipLostError as catch all from persistence layer 

    Cadence history service rely on ShardOwnershipLostError for triggering
unload of the shard.  If persistence layer is unable to detect
ShardOwnershipLost error from Cassandra then it will cause retries
within Timer and Transfer processors and could result in fatal error
causing the entire host to be restarted.
Updating the persistence layer to always return ShardOwnershipLostError
is a catch all when unable to detect the cause of failed transaction to
only cause reload of single shard.
    @samarabbas
    samarabbas committed Jun 21, 2018
    Configuration menu
    Copy the full SHA
    a3386e5 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'master' into persistence-error-conditional-update

    @wxing1292
    wxing1292 authored Jun 21, 2018
    Configuration menu
    Copy the full SHA
    052e77f View commit details
    Browse the repository at this point in the history