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.

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

fix: Retry operations that fail to be re-published #1291

Merged
merged 1 commit into from
May 9, 2022

Conversation

bstasyszyn
Copy link
Contributor

When an operation is NACKED then the operation is re-published to the AMQP queue so that it may be retried. If the operation fails to be published (because the AMQP server is down) then the operation is detached from the current server instance, i.e. the server ID is persisted as 'detached'. The next time the operation monitor task is run, it will attempt to re-publish the operation.

closes #1289

Signed-off-by: Bob Stasyszyn Bob.Stasyszyn@securekey.com

@cla-bot cla-bot bot added the cla-signed label May 9, 2022
@codecov
Copy link

codecov bot commented May 9, 2022

Codecov Report

Merging #1291 (de8958e) into main (159bb53) will decrease coverage by 0.01%.
The diff coverage is 68.11%.

@@            Coverage Diff             @@
##             main    #1291      +/-   ##
==========================================
- Coverage   87.90%   87.89%   -0.02%     
==========================================
  Files         177      177              
  Lines       17650    17683      +33     
==========================================
+ Hits        15516    15542      +26     
- Misses       1363     1366       +3     
- Partials      771      775       +4     
Impacted Files Coverage Δ
pkg/context/opqueue/opqueue.go 82.38% <68.11%> (-0.40%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 159bb53...de8958e. Read the comment docs.

When an operation is NACKED then the operation is re-published to the AMQP queue so that it may be retried. If the operation fails to be published (because the AMQP server is down) then the operation is detached from the current server instance, i.e. the server ID is persisted as 'detached'. The next time the operation monitor task is run, it will attempt to re-publish the operation.

closes trustbloc#1289

Signed-off-by: Bob Stasyszyn <Bob.Stasyszyn@securekey.com>
@bstasyszyn bstasyszyn merged commit 9d7981d into trustbloc:main May 9, 2022
@bstasyszyn bstasyszyn deleted the 1289 branch May 9, 2022 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Operations that fail to be re-published are abandoned
3 participants