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

Handle history not found error when archiving history #2465

Merged
merged 2 commits into from
Feb 5, 2022

Conversation

yycptt
Copy link
Member

@yycptt yycptt commented Feb 4, 2022

What changed?
Skip archival if workflow history not found.

Why?
It's possible that history archiver get multiple requests for archiving the same workflow (e.g. when signal system workflow times out and retry).

Skip archival if workflow history not found. If workflow history not found, we currently return an non-retryable error immediately. It's the same as just return from the Archive method with nil error in terms of behavior since workflow won't retry the non-retryable error. As not found is an expected error, we should not emit non-retryable log/metric.

#2464

How did you test it?
Unit test

Potential risks

Is hotfix candidate?

@yycptt yycptt requested review from yux0 and a team February 4, 2022 20:23
@yycptt yycptt force-pushed the archival-non-exist branch from 841102b to 3ada53e Compare February 4, 2022 20:31
@yycptt yycptt closed this Feb 4, 2022
@yycptt yycptt reopened this Feb 4, 2022
@yycptt yycptt merged commit 8c81dbc into temporalio:master Feb 5, 2022
@yycptt yycptt deleted the archival-non-exist branch February 5, 2022 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants