Skip to content

Fix compatibility issue between older clients and newer workers on DT.AzureStorage - #651

Merged
Chris Gillum (cgillum) merged 2 commits into
mainfrom
cgillum/fix650
Dec 1, 2021
Merged

Chris Gillum (cgillum) merged 2 commits into
mainfrom
cgillum/fix650

Conversation

@cgillum

Copy link
Copy Markdown
Member

Fixes #650.

The fix is to essentially short-circuit out of de-dupe detection if the Instances table has a record with a null value for ExecutionId. This will be true only for orchestrations that are started with clients on v1.8.4 or earlier (ExecutionId wasn't added until after the orchestration checkpointed once). For newer clients that do add ExecutionId when scheduling an orchestration, de-dupe detection should continue to work as normal - no change in behavior.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM with non-blocking nit.

Comment thread src/DurableTask.AzureStorage/OrchestrationSessionManager.cs Outdated
@cgillum

Copy link
Copy Markdown
Member Author

Got an internal customer to independently verify this fix as well.

@cgillum
Chris Gillum (cgillum) merged commit cfb0593 into main Dec 1, 2021
@cgillum
Chris Gillum (cgillum) deleted the cgillum/fix650 branch December 1, 2021 20:34
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.

Orchestrations stuck in Pending when using mismatched versions of DurableTask.AzureStorage

2 participants