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

Do not double execute close execution task if visibility archival is disabled #3072

Merged
merged 1 commit into from
Jul 8, 2022

Conversation

yycptt
Copy link
Member

@yycptt yycptt commented Jul 7, 2022

What changed?

  • Do not double execute close execution task if visibility archival is disabled

Why?

  • For standby task that doesn't have side effect, we don't have to force execute it.

How did you test it?

Potential risks

Is hotfix candidate?

  • Yes

@yycptt yycptt marked this pull request as ready for review July 7, 2022 22:21
@yycptt yycptt requested a review from a team as a code owner July 7, 2022 22:21
return true
case enumsspb.TASK_TYPE_TRANSFER_CLOSE_EXECUTION:
if shard.GetArchivalMetadata().GetVisibilityConfig().ClusterConfiguredForArchival() {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can check per namespace config here as well, but cluster level should be good enough.

@yycptt yycptt requested review from yux0 and yiminc July 7, 2022 22:22
@yycptt yycptt merged commit 7cde1d0 into temporalio:master Jul 8, 2022
@yycptt yycptt deleted the improve-standby-close-task branch July 8, 2022 00:58
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.

None yet

2 participants